-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
JSOUP not sending Proxy-Authorization header #1155
Comments
If the Authenticator method works for you, what's the problem with using that? From my understanding of how this works, the underlying Java Http handler has special case handling for proxy authentication, and if you're not using the Authenticator, it gets pulled out of the request, which is why you're not seeing it in wireshark. |
Sending proxy username and proxy password through header is kinda connection-specific. |
Got it. In your |
Yeah, this is what I'm done so far. Thank you anyway. |
Hi! |
This only occurs when the connection is with HTTPS. When you use multithreading there is no way to use the Default Authenticator if you need different users. Please help us. How to be able to link the credentials for each connection using JSOUP? |
I think still it doesn't have a way to provide credentials apart from using Authenticator (https://docs.oracle.com/javase/7/docs/api/java/net/Authenticator.html#getRequestingHost()), can someone confirm pls? |
Hello, I've been trying to parse page through proxy, but cannot connect to proxy server.
Receiveing error: java.io.IOException: Unable to tunnel through proxy. Proxy returns "HTTP/1.0 407 Proxy Authentication Required"
Here is my code:
And if I use java.net.Authenticator, the connection works OK.
I've read numerous SO threads, the only solution that I've found is using Authenticator.
What am I doing wrong? Please help.
I heve axamined the process with wireshark, and there were no "Proxy-Authorization" header sent at all.
I've also tried setting "Proxy-Authorization" as data and cookies, no result.
While I can use Authenticaor, I think that passing proxy username and password with header should be more convinient.
The text was updated successfully, but these errors were encountered: