-
Notifications
You must be signed in to change notification settings - Fork 555
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
Invalid port number #116
Comments
It's an issue with Addressable. I created an issue sporkmonger/addressable#42 |
Looks like allowing unencoded '#' in password by Addressable could have negative consequences, please see sporkmonger/addressable#42 |
Ok, thanks. I will try to create a proper patch when I have time. |
I re-opened the issue :) |
I looked at it again, but I'm not sure this can be fixed. Let's say we have following uri "us#rn@me:sec//ret?@host.com/". This uri contains forbidden characters in userinfo. We assume that username is us#rn@me and password is sec//ret? But for uri parser it's impossible to recognise where is the start and the end of userinfo. |
Closing this issue since there is no fix imo. I'll be happy to reopen it, if it can be fixed. |
There is a problem when using authentication that has a password that includes a "#" (e.g. E43xb_d#A):
Currently I have monkey patched (added
URI.encode
) it and it works for me:The text was updated successfully, but these errors were encountered: