-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Support NTLM protocol with the proxy: fixed the header name for Proxy-Authorization #563
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
Conversation
Support NTLM protocol with the proxy: fixed the header name for Proxy-Authorization
Thanks!
Will port on master.
Awesome - thank you!
Do you have an ETA on the next 1.8.x release (1.8.10?)? It would be awesome to avoid keeping a fork for any length of time.
Oh, and thanks for this awesome project. We're using it for WebSockets behind proxies, and it's going great so far!
@artnaseef I can cut the release as soon as next week. @slandelle , what do you think?
Whenever you want.
2014年06月06日 0:37 GMT+02:00 Jeanfrancois Arcand notifications@github.com:
@artnaseef https://github.com/artnaseef I can cut the release as soon
as next week. @slandelle https://github.com/slandelle , what do you
think?—
Reply to this email directly or view it on GitHub
#563 (comment)
.
@jfarcand - next week would be excellent! Thank you.
Support for NTLM proxies, using the Netty provider, did not appear to function due to the wrong header name being used on the second request from the client to the server in the handshake:
Authorizationshould beProxy-Authorization.Attached is a pull request that fixes the problem against 1.8.10-SNAPSHOT.
Here's a snippet of code that shows how the NTLM proxy is configured.