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

Proxy-Authenticate scope #331

Closed
mnot opened this issue Mar 19, 2020 · 2 comments · Fixed by #364
Closed

Proxy-Authenticate scope #331

mnot opened this issue Mar 19, 2020 · 2 comments · Fixed by #364

Comments

@mnot
Copy link
Member

mnot commented Mar 19, 2020

P-A is defined as:

The "Proxy-Authenticate" header field consists of at least one challenge that indicates the authentication scheme(s) and parameters applicable to the proxy for this effective request URI (Section 5.5).

This seems really odd -- P-A is not generally used in a way that's specific to a single target URI.

@mnot mnot added the semantics label Mar 19, 2020
@mnot mnot mentioned this issue Mar 19, 2020
3 tasks
@mnot
Copy link
Member Author

mnot commented May 5, 2020

I think it's scoped to the request; i.e., if the client retries the same request with appropriate credentials, it's likely to succeed; we can't say much more than that.

@reschke
Copy link
Contributor

reschke commented May 6, 2020

FTR, the text we have is inherited from https://greenbytes.de/tech/webdav/rfc2616.html#header.proxy-authenticate.

mnot added a commit that referenced this issue May 20, 2020
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