I experienced similar problems with IE5. Try producing redirect
instruction instead (HTTP/1.1 301), or even '200 OK' code with
redirection done either via javascript or meta refresh tag.
al wrote:
>
> Hi,
>
> I am currently running a website which has a user loign module which
> works as follows. A user hits the site for the first time in a browser
> session, an Apache module is called to check if a valid cookie is sent,
> and if not, a '403 Forbidden Access' status is send, and the document
> redirects to an ErrorDoc which processes this (ie assigns the cookie).
>
> The problem is this: when the line 'HTTP/1.1 403 Forbidden' is sent in
> the header to IE5, THAT browser thinks its a really neat idea to produce
> its own document from somewhere on a local Windows machine, instead of
> the one which I have prepared for it. End result, anyone hitting our
> site for the first time in a session using IE5 will be confronted with
> this message.
>
> Now, aside from nuking Microsoft off the face of this planet, a solution
> which I may be partial to given the resources, on a more feasible level,
> is there anything I can do to prevent this problem from occurring?
>
> I would be extremely grateful to anyone who can help me with this, since
> it is quite a frustrating for us.
>
> Thanks in advance.
>
> Regards
>
> --
> ==============================
> Ali Hussein
> Computer Systems Administrator
> World Careers Network
>
> Web: http://www.wcn.co.uk/
> E-mail: mailto:[EMAIL PROTECTED]
> Tel: +44 208 946 9876
> Fax: +44 208 946 9855
> ==============================
--
Eugene Miretskiy <[EMAIL PROTECTED]>
InVision.com, INC. (516) 543-1000
www.invision.net / www.longisland.com
