Welcome to ISAserver.org

Help* IE 7 & 8 freezing through ISA and other Proxies

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA 2006 General] >> General >> Help* IE 7 & 8 freezing through ISA and other Proxies

Page: [1]

Message

<< Older Topic Newer Topic >>

Help* IE 7 & 8 freezing through ISA and other Proxies - 1.Jun.2012 6:21:34 AM

jimjam

Posts: 1
Joined: 1.Jun.2012
Status: offline

Hi all

First post here. I work for an IT company and over the past 2 weeks we are having alot of problems with IE 7 and 8 freezing when accessing certain websites (EDIT: sometimes IE gets wiped out, sometimes it recovers after 5mins).

Note freezing does not happen through Chrome and Firefox, IE 9 seems to be ok too.

I have looked through ISa logs on various solutions and the problem seems to stem from .css files (see below included error code and end of the file)

64 - settings/styles/custom.css
10054 - javascript/datePicker/datepicker_vista/datepicker_vista.css
10054 -webapp/resource/css/screen_static.css
10060 -EDIFBI.css
1460 - css/navlist_arrow.png

Initially this was just one website for one customer but now it has spread to many other websites. My team have done no changes to any of the proxies configurations and its happens through various solution including:

ISA + Finjan
TMG + Finjan
ISA + Websense
Websense V10K
Bluecoat
Scansafe

We are getting bombarded with calls at the moment and even though it is a proxy problem is was not caused by a proxy conifguration change.

We managed to solve the problem on the first website with the web developer, I have posted their solution below: (note there were two problems but we were not aware of the second until the 1st was fixed)

part 1 (whole site affected)
An internet explorer specific stylesheet that is referencing user interface image assets (spinner and borders). This stylesheet is using the AlphaImageLoader filter that loads images from document relative paths as opposed to the css location caused internet explorer to try to retrieve the images from the wrong location causing a 404 response from the server and timing out the page load through the proxy server. This was resolved by updating the stylesheet to contain absolute paths to the images. As this was a global stylesheet it affected the whole site

part 2 (one page affected)
A missing stylesheet that is dynamically requested from the ** section was missing causing a 404 response from the server. This is now resolved by adding an empty stylesheet on the page and going forward the reference to this stylesheet is removed from the codebase and committed in our version control to be rolled out with the next planned site update.

We have also tested the 404 error page on the site and it is setting the correct HTTP response header (404 Not Found) but that the proxy server is marking these as a time-out (1460 This operation returned because the timeout period expired) and is causing the whole page to timeout rather than just the missing resource.

I am just wondering if any else has come accross this, whether this an IE update or whether the websites host have changed their file servers?

I will be grateful for any feedback, advice, etc

Thanks

Regards

Jim

< Message edited by jimjam -- 1.Jun.2012 6:36:15 AM >