3 ms·

Could you please give details about how this broke? What's special about your school internet connection? I tried hard to make SPDY upgrade not break anything a

by agl 15y ago

Could you please give details about how this broke? What's special about your school internet connection? I tried hard to make SPDY upgrade not break anything and we've had very few reports of problems so I'm very interested in what when wrong in your case.

tiles 15y ago
Email sent; I'll be happy to provide logging information where I can. For the record, this may reflect my particular Ubuntu installation, or my room's ethernet port, as no other students have had this problem. Good to know I'm an edge case here.
- agl 15y ago
  I didn't receive it I'm afraid, not even in spam. Sorry to be a bother. agl at chromium dot org should work. Thanks.
gst 15y ago
I don't have the same issue as the original poster, but I also experience some issues with SPDY that don't seem to be a problem with HTTP: For example, my ISP here in Austria drops my IP connection each 8 hours. After reconnecting a new dynamic IP gets assigned to my modem. In addition, the internal network is a NAT and the modem might have some default firewall rules that filter some types of packets. After a new IP gets assigned to my modem Google applications like GMail typically hang for something like 10-15 minutes. I suspect that Chromium does not recognize that the TCP connection is essentially death and that control information that might tell Chromium that this is the case (TCP Reset replies?) are either not sent by Google or are filtered by my modem. I have not experienced this issue with other websites yet, although a similar issue should occur when persistent TCP connections are used. Maybe the timeout for persistent TCP connections is lower or it was just a coincidence because I didn't yet surf on a given website will my connection was reset. If interested I can try to provide some more debugging information or a login to a box within the internal network. See the link in my profile for contact details.

by agl 15y ago

tiles 15y ago

Email sent; I'll be happy to provide logging information where I can. For the record, this may reflect my particular Ubuntu installation, or my room's ethernet port, as no other students have had this problem. Good to know I'm an edge case here.

agl 15y ago
I didn't receive it I'm afraid, not even in spam. Sorry to be a bother. agl at chromium dot org should work. Thanks.

gst 15y ago

I don't have the same issue as the original poster, but I also experience some issues with SPDY that don't seem to be a problem with HTTP: For example, my ISP here in Austria drops my IP connection each 8 hours. After reconnecting a new dynamic IP gets assigned to my modem. In addition, the internal network is a NAT and the modem might have some default firewall rules that filter some types of packets. After a new IP gets assigned to my modem Google applications like GMail typically hang for something like 10-15 minutes. I suspect that Chromium does not recognize that the TCP connection is essentially death and that control information that might tell Chromium that this is the case (TCP Reset replies?) are either not sent by Google or are filtered by my modem. I have not experienced this issue with other websites yet, although a similar issue should occur when persistent TCP connections are used. Maybe the timeout for persistent TCP connections is lower or it was just a coincidence because I didn't yet surf on a given website will my connection was reset. If interested I can try to provide some more debugging information or a login to a box within the internal network. See the link in my profile for contact details.