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.

Sign up for GitHub

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

Jump to bottom

Validation failures #462

Closed
mnot opened this issue Oct 8, 2020 · 0 comments · Fixed by #468
Closed

Validation failures #462

mnot opened this issue Oct 8, 2020 · 0 comments · Fixed by #468
Assignees
@mnot
Labels
caching has-proposal

Comments

@mnot
Copy link
Member

mnot commented Oct 8, 2020

4.3.3 says:

However, if a cache receives a 5xx (Server Error) response while attempting to validate a response, it can either forward this response to the requesting client, or act as if the server failed to respond. In the latter case, the cache may send a previously stored response (see Section 4.2.4).

I think that MAY should be prose, and should also list retrying the request as an option.
@mnot mnot added the caching label Oct 8, 2020
@mnot mnot self-assigned this Oct 8, 2020
mnot added a commit that referenced this issue Oct 9, 2020
@mnot
Reduce MAY to prose and call out retry.
8bc0ea5 
Fixes #462.
@mnot mnot mentioned this issue Oct 9, 2020
Merged
@mnot mnot closed this as completed in #468 Nov 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mnot mnot

Labels
caching has-proposal
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Validation Failures (Mnot 462) httpwg/http-core
1 participant
@mnot