[squid-users] Squid 2.7.STABLE5 hangs with "HEAD" request in LOG

Hi,

i am Thomas from Germany.

We are using a squid 2.7.STABLE5-2.12.16.1 on a 64bit SLES11 for some years.
( I know its not up2date)
 
It runs fine without any problems, but now we have an issue on a specific
website, where a movie file is embedded. - It takes a very long time until
the movie is loaded, with Microsoft Internet Explorer (tested with different
versions of IE.) - When we use Mozilla Firefox the movie is loaded in
seconds.
 
When i click on the embedded movie link within internet explorer, i see in
the squid realtime log that the request hangs with a "496 HEAD" message in
the log and it takes more than a minute before the video starts, here is the
logfile:
 
--SQUID IE LOG------------------------------------------------
1389176557.753 89 pc-number1 TCP_MISS/200 1978 GET
http://www1.wdr.de/mediathek/video/sendungen/lokalzeit/lokalzeit-aus-duesseldorf/videovodafonehauswirdwirtschaftsministerium100-videoplayer_size-L.html
- DIRECT/23.67.138.210 text/html
 
1389176557.845 89 pc-number1 TCP_MISS/200 496 HEAD
http://www.wdr.de/themen/global/flashplayer/wsPlayer.swf -
DIRECT/23.67.138.210 application/x-shockwave-flash
 ------------------------------------------------------------------

And now the same request in firefox, which runs like a charm:

--SQUID Firefox LOG-------------------------------------------
1389176452.779 120 pc-number1 TCP_MISS/200 1978 GET
http://www1.wdr.de/mediathek/video/sendungen/lokalzeit/lokalzeit-aus-duesseldorf/videovodafonehauswirdwirtschaftsministerium100-videoplayer_size-L.html
- DIRECT/23.67.138.210 text/html
 1389176453.099 301 pc-number1 TCP_MISS/200 201977 GET
http://www.wdr.de/themen/global/flashplayer/wsPlayer.swf -
DIRECT/23.67.138.210 application/x-shockwave-flash
 1389176453.837 33 pc-number1 TCP_MISS/200 2015 GET
http://www1.wdr.de/crossdomain.xml - DIRECT/23.67.138.210 application/xml
 1389176453.890 35 pc-number1 TCP_MISS/200 1355 GET
http://www1.wdr.de/mediathek/resources/flash/skin/cfg.xml -
DIRECT/23.67.138.210 application/xml
 1389176454.061 84 pc-number1 TCP_MISS/200 448 GET
http://www1.wdr.de/mediathek/resources/flash/skin/_dc.gif -
DIRECT/23.67.138.210 image/gif
 1389176454.089 112 pc-number1 TCP_MISS/200 6242 GET
http://www.wdr.de/themen/global/flashplayer/wsControls.swf -
DIRECT/23.67.138.210 application/x-shockwave-flash
 1389176454.231 254 pc-number1 TCP_MISS/200 1919 GET
http://www.wdr.de/themen/global/flashplayer/loading_logo_r.swf -
DIRECT/23.67.138.210 application/x-shockwave-flash
 1389176454.232 112 pc-number1 TCP_MISS/200 4026 GET
http://www1.wdr.de/mediathek/resources/flash/skin/play.png -
DIRECT/23.67.138.210 image/png
 1389176454.281 318 pc-number1 TCP_MISS/200 273476 GET
http://www.wdr.de/themen/global/flashplayer/plugins/AkamaiAdvancedStreamingPlugin-v3.10-osmf2.0.swf
- DIRECT/23.67.138.210 application/x-shockwave-flash
 ------------------------------------------------------------

Anyone an idea, what it means, that squid stops with the "HEAD" request in
the logfile ?
 
Kind regards
Thomas

--
View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-2-7-STABLE5-hangs-with-HEAD-request-in-LOG-tp4664219.html
Sent from the Squid - Users mailing list archive at Nabble.com.