Skip to content
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

Combining Partial Content #458

Closed
mnot opened this issue Oct 2, 2020 · 3 comments · Fixed by #526
Closed

Combining Partial Content #458

mnot opened this issue Oct 2, 2020 · 3 comments · Fixed by #526

Comments

@mnot
Copy link
Member

mnot commented Oct 2, 2020

3.4 says:

When combining the new response with one or more stored responses, a cache must use the header fields provided in the new response, aside from Content-Range, to replace all instances of the corresponding header fields in the stored response.

As per other discussions, this needs to be more nuanced; either a reference to 4.3.4, or new text.

@mnot mnot added the caching label Oct 2, 2020
@mnot mnot self-assigned this Oct 8, 2020
@mnot
Copy link
Member Author

mnot commented Oct 22, 2020

The tests show that no one is really doing this; HEAD is either converted to a GET on the backend, or it doesn't seem to touch the cache.

I think the most sane thing to do is to refer to the rules for a 304 update, but make it clear that this is optional.

@reschke
Copy link
Contributor

reschke commented Oct 22, 2020

Could you clarify how HEAD is relevant for "Combining Partial Content"?

@mnot
Copy link
Member Author

mnot commented Oct 22, 2020

Arg, sorry, wrong issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

2 participants