-
Notifications
You must be signed in to change notification settings - Fork 885
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
Cannot visit some http1.1 website under caddy+forwardproxy setup #537
Comments
Root cause similar to http-party/node-http-proxy#529 |
nice catch, I can verify the below primitive patch works for this url
EDIT: even better, taking care of redirect url which might contains 'http://' or 'https://' as well.
|
I use GURL to parse the request URI. See if you can review the following: naiveproxy/src/net/tools/naive/http_proxy_server_socket.cc Lines 325 to 429 in c942f02
|
yeah, better. |
I am not so sure, but what if path component could be empty in absoluteURI? what about:
|
I cannot figure out what's the meaning by the comment of GURL:
|
I was using naiveproxy to visit some server website which have some server settings, such as:
I got a 403 error. Without the proxy, it returned OK. Call curl directly from the serer, it returned OK.
Checked with naiveproxy client:
Checked with the server (with tcpdump):
The naiveproxy had removed the header such asProxy-Connection
but the server (caddy+forwardproxy) added it again. I checked with forwardproxy code, it should be removed by design.I don't know how it happened, the request is correct except for Referer request. So, still investigating.
caddy version:
naiveproxy version:
The text was updated successfully, but these errors were encountered: