The 1.0 release of Google Chrome has everyone abuzz.\u00a0 Here at NI, loads of people are adopting it.\u00a0 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.\u00a0 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\u00a0 “Error 320 (net::ERR_INVALID_RESPONSE): Unknown error.”<\/p>\n
At first, it seemed like if people reloaded or cleared cache the problem went away.\u00a0 It turned out this wasn’t true – we have two load balanced servers in a cluster serving this site.\u00a0 One server worked in Chrome and the other didn’t; reloading or otherwise breaking persistence just got you the working server for a time.\u00a0 But both servers worked perfectly in IE and Firefox (every version we have lying around).<\/p>\n
So we started researching.\u00a0 Both servers were as identical as we could make them.\u00a0 Was it a Confluence bug?\u00a0 No, we have phpBB on both servers and it showed the same behavior – so it looked like an Apache level problem.<\/p>\n
Sure enough, I looked in the logs.\u00a0 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).\u00a0 Both boxes had an identically compiled Apache 2.0.61.\u00a0 I diffed all the config files- except for boxname and IP, no difference.\u00a0 The problem persisted for more than a week.<\/p>\n
We did a graceful Apache restart for kicks – no effect.\u00a0 Desperate, we did a full Apache stop\/start – and the problem disappeared!\u00a0 Not sure for how long.\u00a0 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…\u00a0 But it’s strange there would be an Apache-end problem that only Chrome would experience.<\/p>\n
I see a number of posts out there in the wide world about this issue; people have seen this Chrome behavior in YouTube, Lycos, etc.\u00a0 Mostly they think that reloading\/clearing cache fixes it but I suspect that those services also have large load balanced clusters, and by luck of the draw they’re just getting a “good” one.<\/p>\n
Any other server admins out there having Chrome issues, and can confirm this?\u00a0 I’d be real interested in knowing what Web servers\/versions it’s affecting.\u00a0 And a packet trace of a “bad” hit would probably show the root cause.\u00a0 I suspect for some reason Chrome is partially sending the cookie or whatnot, choking the hit.<\/p>\n","protected":false},"excerpt":{"rendered":"
The 1.0 release of Google Chrome has everyone abuzz.\u00a0 Here at NI, loads of people are adopting it.\u00a0 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.\u00a0 They’d hit a page and get a terse error, […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[196,96],"tags":[206,207,205,208],"class_list":["post-162","post","type-post","status-publish","format-standard","hentry","category-browsers","category-software-and-tools","tag-apache","tag-bug","tag-chrome","tag-error"],"aioseo_notices":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pfI0c-2C","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.webadminblog.com\/index.php\/wp-json\/wp\/v2\/posts\/162","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.webadminblog.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.webadminblog.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.webadminblog.com\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.webadminblog.com\/index.php\/wp-json\/wp\/v2\/comments?post=162"}],"version-history":[{"count":3,"href":"https:\/\/www.webadminblog.com\/index.php\/wp-json\/wp\/v2\/posts\/162\/revisions"}],"predecessor-version":[{"id":164,"href":"https:\/\/www.webadminblog.com\/index.php\/wp-json\/wp\/v2\/posts\/162\/revisions\/164"}],"wp:attachment":[{"href":"https:\/\/www.webadminblog.com\/index.php\/wp-json\/wp\/v2\/media?parent=162"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.webadminblog.com\/index.php\/wp-json\/wp\/v2\/categories?post=162"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.webadminblog.com\/index.php\/wp-json\/wp\/v2\/tags?post=162"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}