Hey Thomas,
The main issue is that the file "request" is kind of "stuck".
We need first to verify the issue which is not even clear enough.
Squid 2.7 OK then.
An update is preferred for comfort reasons but assuming there is another
issue for now.
Squid 2.7 is not in the support life time but I will try to eliminate
couple aspects about the issue.
Leaving firefox or explorer is smart.
Squid operates at the network level which is not even related to the
browser in the manner of "networking".
The browser uses squid to "get" content.
In a case you have a specific web site or specific issue try couple things:
Open firefox "private windows" which will use clean surfing no local
caching and other stuff.
Also remove any addons that runs on the browser.
Once it's up open the profiling and inspection interface in FF using:
Tools > Web Developer > Profiler.
it can also be shown with shift+f5
There you have a network tab which shows every detail about the page and
related content load.
enter a web site name and see what happens.
You should see how long it take between each request to load.
This level will show couple basic levels that can be understood fast.
I do not know what the network design and looks is so I would not even
assume couple things about the network infrastructure.
Since it's SLES11 I assume this node has 1Gbps network connection but
still Unsure.
The reasons for what you see can be couple and to make sure one step at
a time you will need to download this file using a simple software like
"wget" for example.
vwget(VisualWget) was built for windows.
The issue possibly not related directly to squid.
In this case that IE and Firefox do not load the content on the same
machine while using the same proxy and it reproducible it's something
that we can say "this" and then and only then we can see that squid 2.7
probably is OK while using only http\1.0.
The access log for example will write and show the log line after the
client received, from squid point of view, the whole response.
You can try to profile the site and see what happens to make sure that
there is or there isn't any issue.
Can you share the client machine hardware and software specs?
Can you share the server machine hardware specs?
Eliezer
On 10/01/14 14:21, 4eversr wrote:
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.
