Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
IPv6 addresses
See original GitHub issueI’m able to http -h 173.194.33.34 and get a valid response, but using http -h 2607:f8b0:400a:801::100e produces the following for me:
http: error: LocationParseError: Failed to parse: Failed to parse: 2607:f8b0:400a:801::100e
It would seem that httpie doesn’t support direct IPv6 address input as http -h ipv6.google.com works fine.
Issue Analytics
- State:
- Created 10 years ago
- Comments:8 (2 by maintainers)
Top Results From Across the Web
IPv6 address - Wikipedia
An Internet Protocol Version 6 address (IPv6 address) is a numeric label that is used to identify and locate a network interface of...
Read more >IPv4 and IPv6 address formats - IBM
An IPv6 (Normal) address has the following format: y : y : y : y : y : y : y : y...
Read more >IPv6 Addressing Overview - System Administration Guide
An IPv6 address is 128 bits in length and consists of eight, 16-bit fields, with each field bounded by a colon. Each field...
Read more >IPv6 Explained for Beginners - Steve's internet Guide
An Ipv6 address uses 128 bits as opposed to 32 bits in IPv4. ... Because an hexadecimal number uses 4 bits this means...
Read more >Test your IPv6.
This will test your browser and connection for IPv6 readiness, as well as show you your current IPv4 and IPv6 address.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The requests bug is fixed and this works now 🎉
@faheel the Requests bug was resolved, it seems there’s some other bug is at play the URL constructed. The correct URL is
http://[2606:4700::6812:748]