-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Add support for safe HTTP preference - RFC 8674 #34847
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
Is a default value of |
@cjunge I'm not sure to understand where this default value would be. Do you mean in the request or in the response? Anyway, from what I understand from the RFC:
There is no such thing as "prefering a not safe content" or sending a response with "preference not applied". |
Comments fixed and PR rebased 😉 |
Oups, wait, tests fail. |
Oups, sorry, tests should be green now |
Thank you @pyrech. |
This PR was merged into the 5.1-dev branch. Discussion ---------- Add support for safe HTTP preference - RFC 8674 | Q | A | ------------- | --- | Branch? | master | Bug fix? | no | New feature? | yes | Deprecations? | no | Tickets | - | License | MIT | Doc PR | - [RFC 8674](https://tools.ietf.org/html/rfc8674) (not a IETF standard at the moment) defines a way for user agents to ask for "safe" content to a server. This PR add helper methods to : - know if the user agent prefers a safe content - mark the response as safe Commits ------- 7f2cef7 Add support for safe preference - RFC8674
This PR was merged into the master branch. Discussion ---------- Add documentation for RFC 8674 support Add documentation for the PR symfony/symfony#34847 Fix #12915 Commits ------- 54d06f5 Add documentation for RFC 8674 support
RFC 8674 (not a IETF standard at the moment) defines a way for user agents to ask for "safe" content to a server. This PR add helper methods to :