-
Notifications
You must be signed in to change notification settings - Fork 10.1k
chore: Fix redirected MDN URLs for HTTP headers docs #21499
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| * **Strict** - Cookies will only be sent in a first-party context and not be sent along with requests initiated by third party websites. | ||
|
|
||
| Refer to the [Mozilla documentation](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) for more information. | ||
| Refer to the [Mozilla documentation](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Set-Cookie#samesitesamesite-value) for more information. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/SameSite is not a sub-page now, so I'm linking to #samesitesamesite-value anchor. There's another occurrence below, I believe
| ## Background | ||
|
|
||
| The [`SameSite` attribute of a cookie](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) specifies whether that cookie can be shared with other domains that load on the same page (ad banners, iFrames). By default, browsers do not send cookies on cross-site subrequests to prevent attackers from stealing or manipulating information present in your cookies. | ||
| The [`SameSite` attribute of a cookie](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Set-Cookie/SameSite) specifies whether that cookie can be shared with other domains that load on the same page (ad banners, iFrames). By default, browsers do not send cookies on cross-site subrequests to prevent attackers from stealing or manipulating information present in your cookies. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See comment above:
| The [`SameSite` attribute of a cookie](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Set-Cookie/SameSite) specifies whether that cookie can be shared with other domains that load on the same page (ad banners, iFrames). By default, browsers do not send cookies on cross-site subrequests to prevent attackers from stealing or manipulating information present in your cookies. | |
| The [`SameSite` attribute of a cookie](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Set-Cookie#samesitesamesite-value) specifies whether that cookie can be shared with other domains that load on the same page (ad banners, iFrames). By default, browsers do not send cookies on cross-site subrequests to prevent attackers from stealing or manipulating information present in your cookies. |
|
Congratulations @bsmth, the maintainer of this repository has issued you a holobyte! Here it is: https://holopin.io/holobyte/cm98nikv303040cl5sdkdzx27 This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account. |
* chore: Fix redirected MDN URLs for HTTP headers docs * chore: Fix redirected MDN URLs for HTTP status docs * chore: Fix redirected MDN URLs for HTTP methods docs
Summary
The MDN HTTP reference docs have a new scheme. The following sections have a
Reference/prefix now:So, the new scheme looks like:
Redirects are in place on MDN for all existing URLs, but we should update the URL prefix used to avoid sending readers to 301s.
See also:
Screenshots (optional)
N/A
Documentation checklist