G
Guest
Hi, I’m having a bit of a problem with how IE 6 interacts with our web
filter, WebSense.
When a user tries to brows to a restricted site they are blocked by WebSense
and receive a page informing them why they were blocked. When they use the
‘back’ arrow the previous website is displayed however if they try to follow
any subsequent link from the site they are met with a 404 error saying that
the page could not be found.
If they close that browser, open a fresh window and go back to the site
everything works ‘as advertised’ unless they follow another blocked link.
I have also noticed that if you wait for a couple of minutes after using the
back arrow to the site it once again works as normal.
This problem does not occur in the Firefox or Opera browser so leads me to
think that it is IE 6 that is caching something or has a longer refresh time
rather than the problem being with the WebSense server/software.
I’d be grateful if any guru out there can shed some light on this or point
me in the right direction.
Cheers now
IainM
filter, WebSense.
When a user tries to brows to a restricted site they are blocked by WebSense
and receive a page informing them why they were blocked. When they use the
‘back’ arrow the previous website is displayed however if they try to follow
any subsequent link from the site they are met with a 404 error saying that
the page could not be found.
If they close that browser, open a fresh window and go back to the site
everything works ‘as advertised’ unless they follow another blocked link.
I have also noticed that if you wait for a couple of minutes after using the
back arrow to the site it once again works as normal.
This problem does not occur in the Firefox or Opera browser so leads me to
think that it is IE 6 that is caching something or has a longer refresh time
rather than the problem being with the WebSense server/software.
I’d be grateful if any guru out there can shed some light on this or point
me in the right direction.
Cheers now
IainM