Issue 138: Error 320 (net::ERR_INVALID_RESPONSE) on HTTP header field continuation (rgs.tamu.edu and ogs.tamu.edu) http://code.google.com/p/chromium/issues/detail?id=138
Comment #20 by xfurious: I dunno if it's the same problem but I can't access facebook.com nor php.net with Chrome, both landing me at a 320 error. I'm updated to the Chrome dev channel and it has not really changed things. Right after the update I got php.net to load once but facebook would not. Then I cleared my cookies and got PHP.net to load but facebook would not. Pressing refresh on either page after it loaded successfully was enough to go back to 320 errors. My advice to the chrome developers: Drop WinHTTP and write your own stack, or better grab an open source one. On a side note: stop blocking the page content sent with 404 errors and other such things. That's just evil. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
