Commit d83bfb2

authored

refactor: Updated RFC spec Safe Methods URL in Cookies chapter

1 parent 5ab1ce2 commit d83bfb2Copy full SHA for d83bfb2

File tree

-1

lines changed

-1

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
@@ -239,7 +239,7 @@ Lax mode, just like `strict`, forbids the browser to send cookies when coming fr
`239`	`239`	A `samesite=lax` cookie is sent if both of these conditions are true:
`240`	`240`	`1. The HTTP method is "safe" (e.g. GET, but not POST).`
`241`	`241`
`242`		`- The full list of safe HTTP methods is in the [RFC7231 specification](https://tools.ietf.org/html/rfc7231). Basically, these are the methods that should be used for reading, but not writing the data. They must not perform any data-changing operations. Following a link is always GET, the safe method.`
	`242`	`+ The full list of safe HTTP methods is in the [RFC7231 specification](https://tools.ietf.org/html/rfc7231#section-4.2.1). Basically, these are the methods that should be used for reading, but not writing the data. They must not perform any data-changing operations. Following a link is always GET, the safe method.`
`243`	`243`
`244`	`244`	`2. The operation performs a top-level navigation (changes URL in the browser address bar).`
`245`	`245`

Comments

(0)