Bugzilla – Bug 1755
SlimServer doesn't work with Firefox/Mozilla with pipelining enabled
Last modified: 2008-08-18 10:54:16 UTC
If a Firefox or Mozilla user has http pipelining enabled, the slim server web interface becomes unusable. Pages never display. Clicking a new link in the web interface starts the throbber ticking (loading icon in top right of browser window) and the browser says Loading..., but the new page never displays. This can be fixed by disabling pipelining, but this is a global setting so degrades performance for all web pages visited. SlimServer may be claiming to support pipelining when it in fact does not. Pipelining is apparently a HTTP 1.1 feature. SlimServer reports itself as HTTP1.x, which probably isn't valid. By reporting itself as 1.0, this may stop Mozilla/Firefox from trying to use pipelining. For more information, see http://forums.slimdevices.com/showthread.php?t=14907. To turn off http pipelining in Mozilla/Firefox as a workaround: - type about:config into the location bar - search for network.http.pipelining - change the value to false Pipelining is a hidden feature in Firefox that is disabled by default. However, turning it on is a well known speed tweak.
I have had this problem, too, which I'd commented on separately under bug #1699 as I believed that described my problem at the time. Turning off pipelining certainly solves the problem for me, which was causing the web interface to hang under Firefox 1.0.4 on Windows, with a Linux server. When it hung in this way the Squeezebox continued to work fine - it just hung up the web interface. IE has always worked fine, and didn't suffer this same problem.
dan committed a fix for this at change 3618. no pipelining support, but should now return proper info for pipelining to be enabled in Firefox/Mozilla Please confirm, re-open if issues still exist.
This bug was marked resolved in Slimserver 6.1, which is several versions ago. If you're still seeing this bug, please re-open it. Thanks!