-
Notifications
You must be signed in to change notification settings - Fork 191
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
Ipv6 support #34
Ipv6 support #34
Conversation
Looks good Filipe, I'll try testing it and include it after that. I'll cheers On 16 March 2011 18:35, fdmanana <
|
One last finding, is that ibrowse_lib:parse_url/1 doesn't parse IPv6 address - once it finds ":" it assumes that what follows is a port number. It's just a matter of integrating it :) |
Ah and here is an interesting discussion about URL parsing with IPv6 address literals and port numbers: http://lists.w3.org/Archives/Public/www-talk/1996JulAug/0088.html Will try it when I get the time, possibly not anytime soon. |
Thanks for digging all this out! I'll see if I can do it myself, otherwise I cheers On 30 March 2011 12:25, fdmanana <
|
As specified in the following RFC: http://www.ietf.org/rfc/rfc2732.txt
inet:gethostbyname/1 might fail for IPv6 literals, therefore check first if host is an IPv6 address literal.
Hi again Chandru, I just added support for IPv6 literals in hostnames when using ibrowse_lib:parse_url/1 Commits and Note that I added a new eunit test for ibrowse_lib:parse_url/1, somehow it feels more natural (and standard) than adding it to ibrowse_test.erl. Let me know what you think. cheers |
This change upgrades ibrowse to version 2.2.0. This version adds support for IPv6 (cmullaparthi/ibrowse#34). This is part of COUCHDB-665. git-svn-id: https://svn.apache.org/repos/asf/couchdb/trunk@1091709 13f79535-47bb-0310-9956-ffa450edef68
This change upgrades ibrowse to version 2.2.0. This version adds support for IPv6 (cmullaparthi/ibrowse#34). This is part of COUCHDB-665. git-svn-id: https://svn.apache.org/repos/asf/couchdb/trunk@1091709 13f79535-47bb-0310-9956-ffa450edef68
Hi Chandru,
Haven't tested it yet, but I think this is a useful addition.
Have you already tried using ibrowse against an IPv6-only host? Sometimes the user may be clueless about whether the remote host is IPv6-only or not, so detecting that and adding the int6 parameter if necessary seems reasonable to do.
regards