Sounds un-fun.
If you capture a sample request via fiddler / wireshark (plugins / dev
utilities for ie) I can at least tell you what is going wrong. I'm
less sure I can tell you how to fix it. I'm semi familiar with squid -
but this doesn't sound like the same kind of situation.
On 3/23/07,
Maximilian,
Now we fond another posting
http://www.nabble.com/Why-is-IE6-freezing--tf3377078.html#a9399366
that reports the excat same problem, but the solution given seems
not to
work for us.
You referred to my posting. Here are comments on quotes of it:
On 20 mar 2007, at 18.30,
Please, go ahead and add a JIRA request for this - describing what you have
in mind...
Andreas Pardeike
PS: I would really love to see some error checking on this. It's
really hard
to catch any errors resulting from asset linking problems.
--
--
Andreas Andreou -
IE is a little less forgiving with javascript errors, so if you get
one all other code will be skipped. (a lot of the time)
I fixed what was a very subtle IE specific bug recently in
4.1.2-SNAPSHOT. You may try that just to see . ...I only have IE7
available to me right now, but should be able
