Skip to content

[HttpFoundation] no 304 response if method is not cacheable #20218

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

Merged
merged 1 commit into from
Oct 14, 2016

Conversation

xabbuh
Copy link
Member

@xabbuh xabbuh commented Oct 14, 2016

Q A
Branch? 2.7
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets
License MIT
Doc PR

Since #19321 OPTIONS and TRACE are considered safe methods. But both methods should not lead to "304 Not modified" responses.

@xabbuh xabbuh changed the title no 304 response if method is not cacheable [HttpFoundation] no 304 response if method is not cacheable Oct 14, 2016
@dunglas
Copy link
Member

dunglas commented Oct 14, 2016

👍

@fabpot
Copy link
Member

fabpot commented Oct 14, 2016

Thank you @xabbuh.

@fabpot fabpot merged commit 3d6b450 into symfony:2.7 Oct 14, 2016
fabpot added a commit that referenced this pull request Oct 14, 2016
…e (xabbuh)

This PR was merged into the 2.7 branch.

Discussion
----------

[HttpFoundation] no 304 response if method is not cacheable

| Q             | A
| ------------- | ---
| Branch?       | 2.7
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets |
| License       | MIT
| Doc PR        |

Since #19321 OPTIONS and TRACE are considered safe methods. But both methods should not lead to "304 Not modified" responses.

Commits
-------

3d6b450 no 304 response if method is not cacheable
@xabbuh xabbuh deleted the not-modified-not-cacheable-method branch October 14, 2016 14:13
This was referenced Oct 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants