-
Notifications
You must be signed in to change notification settings - Fork 142
-
Notifications
You must be signed in to change notification settings - Fork 142
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 and .pac interaction #62
Comments
Yeah. Alt-Sv is for finding an origin, not for finding a proxy -- a proxy might use it, though. This should all be clear based upon reading of RFC7230, but if not we could add a sentence or two to clarify. |
Is there something we need to do here? |
Maybe we need to specify an alternative to pac files or define how to Regards, On 30.04.2015 16:31, Julian Reschke wrote:
|
For this spec, I think we could just add a sentence to the effect that 'clients configured to use a proxy SHOULD NOT use alternative services." |
Add: "A client configured to use a proxy for a given request SHOULD NOT send it to an alternative service, but instead use that proxy." |
Modification: "A client configured to use a proxy for a given request SHOULD NOT directly connect to an alternative service for it, but instead route it through that proxy." |
(seems the discussion on the mailing list hasn't come to a conclusion) |
It did regarding this issue, I think; the remaining discussion is a tangent. |
Ryan asks what you should pass to proxy.pac when you know about a potential alt-svc.
I suggested that you use the original request origin and only use alternatives if the proxy.pac doesn't provide a proxy address. That is proxy.pac overrides alternative services.
The text was updated successfully, but these errors were encountered: