Closed GoogleCodeExporter closed 8 years ago
Probably caused by IPv6.
1) Does your windows box support IPv6 ?
2) What is the result of "Socket.getAddrInfo('www.google.com',
Socket.PF_INET6)" ?
3) Does the HTTP client work, if you force IPv4? You can try that by adding
"throw 1;" at the end of the line 305 in lib/http.js
Original comment by ondrej.zara
on 11 Jun 2012 at 5:36
My Windows box doesn't support IPv6. As far as I know, Windows did not
support this until Vista, and I am on XP.
The result of `Socket.getAddrInfo('www.google.com', Socket.PF_INET6)` is an
empty string, with no exception thrown. Adding `throw 1` after line 305
didn't help, it still throws the same error..
Let me know if you'd like me to try this on Windows 7 or Mac OS.
Original comment by simon.st...@gmail.com
on 11 Jun 2012 at 12:29
I managed to reproduce the bug (WinXP), so there is no need to try on Win7.
(Note: it is possible to add IPv6 support to XP; just install it as a new
protocol in Network Connections)
The question is, what should be the correct behavior of getAddrInfo. Target
hostname (www.google.com) HAS a valid AAAA (IPv6) record, so getAddrInfo should
probably not fail. On the other hand, Windows is unable to successfully resolve
this record, rendering the getAddrInfo call useless.
What is your opinion?
Original comment by ondrej.zara
on 11 Jun 2012 at 12:45
The current behaviour of returning an empty string my be fine. In that case
we would just need to adjust the logic in http.js to account for this case.
I'll have a play with it and see what I come up with. I assume we need to
keep the try/catch for cases where it might throw (not sure what this would
be).
Original comment by simon.st...@gmail.com
on 11 Jun 2012 at 7:00
Yes, the try-catch must remain there. getAddrInfo throws when the DNS record
was not found; when the DNS server is not available; when any other kind of
network problems occurs...
Original comment by ondrej.zara
on 11 Jun 2012 at 8:57
Original comment by ondrej.zara
on 16 Jul 2012 at 8:27
http://code.google.com/p/teajs/issues/detail?id=5
Original comment by ondrej.zara
on 20 Jul 2012 at 7:49
Fixed in http://code.google.com/p/teajs/issues/detail?id=5.
v8cgi is now known as TeaJS, please update your bookmarks accordingly :-)
Original comment by ondrej.zara
on 30 Jul 2012 at 7:49
Original issue reported on code.google.com by
simon.st...@gmail.com
on 11 Jun 2012 at 2:45