http://bugzilla.novell.com/show_bug.cgi?id=536591 Summary: squid returns 411 content length required when firefox POSTS without a body Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jnelson-suse@jamponi.net QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.0.13) Gecko/2009080200 SUSE/3.0.13-0.1.2 Firefox/3.0.13 POSTing without a body is perfectly legal. Firefox *should* set the content-length header to 0 in this case, but it doesn't (it omits the header entirely). However, while Apache treats this as OK, lighttpd and IIS (and others) do not. Furthermore, squid actually preemptively returns an error in this case! Two things should change: 1. squid should be more lenient, or should add a content-length: 0 header. 2. firefox should add a content-length: 0 header when there is no body. I am using squid 2.7-STABLE5-1.20.1 on openSUSE 11.1 I am using firefox MozillaFirefox-3.0.13-0.1.2 on openSUSE 11.1 You can read all about it here: http://www.google.com/search?hl=en&q=firefox%20post%20missing%20content-length Note, I filed the bug under squid because at least *some* servers will continue to work. Specifically, a number (actually, a *lot* ) of java and javascript applications make null POSTs which *only* fail when going through squid, because the apps themselves are running under apache (or tomcat). Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.