Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upLoading full HTML specification occasionally waits for 2 minutes before initiating the network request #11038
Comments
|
Amazingly Instruments.app claims that it's sitting blocked inside TcpStream::connect for the entire duration of the wait. |
|
It seems to be an IPv6 issue with whatwg servers.
A network capture shows that TCP SYN packets sent over IPv6 don't get any reply. When we fallback to IPv4, the connection is properly established. This is not a servo issue :) |
|
On the other hand, other browsers do not exhibit this problem, so presumably there's some way to mitigate it. |
|
There is a preference on Firefox which is called A similar mechanism could be added to Servo. But I suppose hyper should be in charge of handling such fallback. |
|
@seanmonstar What are your feelings about a non-IPv6 fallback API? |
|
@jdm That'd be really neat. It's also not something that can done in You'd need |
|
Is this still an issue, given we bumped Hyper etc? |
|
Yes. |
|
Related: hyperium/hyper#1316 |
|
I believe this has been fixed now with the update to hyper 0.12. @jdm can you confirm? |
Wireshark confirms the preposterous title. When I run
./mach run -r https://html.spec.whatwg.org/, I get a grey window for two minutes before any content appears. Wireshark shows no traffic between my machine and html.spec.whatwg.org before that point. I've only been able to reproduce this on my macbook so far, not my desktop linux machine.