Chrome Error 320 Net Err_invalid_response
Contents |
from GoogleSign inHidden fieldsSearch for groups or messages
of people are adopting it. Shortly after it went gold, we started to hear from users that they were having problems with our internal collaboration solution, based on the Atlassian Confluence wiki product. They'd hit a page and get a terse error, which if you clicked on "More Details" you got the slightly more helpful, or at least Googleable, string "Error 320 (net::ERR_INVALID_RESPONSE): Unknown error." At first, it seemed like if people reloaded or cleared cache the problem went away. It turned out this wasn't true - we have two load balanced servers in a http://productforums.google.com/d/topic/chrome/WS26mFrtvDs cluster serving this site. One server worked in Chrome and the other didn't; reloading or otherwise breaking persistence just got you the working server for a time. But both servers worked perfectly in IE and Firefox (every version we have lying around). So we started researching. Both servers were as identical as we could make them. Was it a Confluence bug? No, we have phpBB on both servers http://www.webadminblog.com/index.php/2008/12/18/google-chrome-hates-you-error-320/ and it showed the same behavior - so it looked like an Apache level problem. Sure enough, I looked in the logs. The error didn't generate an Apache error, it was still considered a 200 OK response, but when I compared the log strings the box that Chrome was erroring on showed that the cookie wasn't being passed up; that field was blank (it was populated with the cookie value on the other box and on both boxes when hit in IE/Firefox). Both boxes had an identically compiled Apache 2.0.61. I diffed all the config files- except for boxname and IP, no difference. The problem persisted for more than a week. We did a graceful Apache restart for kicks - no effect. Desperate, we did a full Apache stop/start - and the problem disappeared! Not sure for how long. If it recurs, I'll take a packet trace and see if Chrome is just not sending the cookie, or sending it partially, or sending it and it's Apache jacking up... But it's strange there would be an Apache-end problem that only Chrome would experience. I see a number of posts out there in the wide world about this issue; people have s
from GoogleSign inHidden fieldsSearch for groups or messages
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up PDF Generation Results in ERR_INVALID_RESPONSE in Chrome up vote 8 down vote favorite 1 When generating a PDF in the browser programmatically (via PHP) the rendered PDF displays fine in both Firefox and Safari, but Chrome returns an ERR_INVALID_RESPONSE. It is a valid PDF - can be opened locally with Adobe Reader/Preview once saved from the working browsers, and will even open in Chrome once the PDF is saved from a different browser. The PDF file is being read through file_get_contents(), is given a current timestamp and then passed to the browser. A workaround would involve saving the file to a temporary spot and redirecting the user (for Chrome, at least) but this is not ideal. I've researched it and only been able to find bug reports dating from 2008. I have an inkling it's a header error. After the PDF is generated, the following headers are sent to the browser (again working fine in FF, Safari and IE): header('Content-type:application/pdf'); header("HTTP/1.1 200 OK"); I've also tried adding the following headers after searching on Stack Overflow, but to no avail: header("Content-Transfer-Encoding: binary"); header('Accept-Ranges: bytes'); Are there missing headers that Chrome requires? Does anyone have experience with getting dynamically generated PDFs to display in Chrome? EDIT: One of my more salient questions is what could be causing this to work fine locally in Chrome, but wouldn't work on a server environment. Thank you in advance for any help. php google-chrome pdf share|improve this question edited Jan 7 at 18:51 asked Jan 4 at 20:27 Andrew Klatzke 354213 Have you tried changing the disposition to attachment? header('Content-Disposition: attachment;; filename="YourFileName"'); –HNA Jan 4 at 20:33 @HNA I have - the same error results in Chrome whe