-
-
Notifications
You must be signed in to change notification settings - Fork 74
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
Escaping of user info breaks NTLM authentication #219
Comments
Did you try other implementations of PSR-7? AFAIK, they all encode the I feel like the correct course of action is to pass |
I've tried laminas and realized it didn't work but it has worked fine with the library. So your solution is for me to go and modify buzz? It's a bit annoying that with this change there is no popular psr-7 implementation that can be used to talk to Microsoft's stuff. |
Buzz is clearly relying on an unspecified behavior yes... |
(you can pin nyholm/psr7 to |
Please link back if you do anything on another repo! |
My reason for using this library was because it was following the psr and that says nothing about escaping the username and password. And the psr say that the What you say is that ofc it should escape it and if I want to use it in any other way I need to know how it's been escaped and revers it instead of getting what I passed in. I feel like that's the definition of insanity. |
I'm sorry for the confusion. You might want to check php-fig/fig-standards#1298 as a follow up. The previous behavior wasn't correct either, as shown when doing |
I figured out a more seamless way to produce non-broken URLs, see #221 |
Thank you for improving and fixing this |
The change in #213 breaks ntml based authentication when specifying a domain.
When using ntml auth it's common to have a domain that is part of the username like this
The slash is not suppose to be escaped and if it's the authentication fails
The text was updated successfully, but these errors were encountered: