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
Secondary resource representation not available #7
Comments
A few thoughts about some possible guidelines for a solution we can discuss:
|
I'll try an approach in which we piggy-back this information to the GET request, using Link header fields. Such as:
with relation types for the common use cases we find. |
Quite straight forward and a got starting point. More complex approaches like the report URI in CSP seem not applicable yet. Agree this is the first thing to try out. |
The current draft states "retry the request to the origin server without including
"out-of-band" in the Accept-Encoding request header field". What if the resource was not available because of the origin server deliberately having removed it using a separate procedure? In that case, the origin server may want to have the client use another secondary server?
The text was updated successfully, but these errors were encountered: