Jan-Henrik Haukeland <[EMAIL PROTECTED]> writes:

> Connecting to www.dowearysoftware.com:443
> HTTP/1.1 200 OK
> Content-Length: 5575
> Content-Type: application/octet-stream
> Content-Location: https://www.dowearysoftware.com:443/index.jsp

Ah, yes, as you can see the server sets the Content-Location header
(i.e. redirect) wrongly in a 200 response. IE must (wrongly) follow
this location leading to a indefinitely redirect loop, that's why your
browser hangs. This is not a tomcat problem but a
IIS/jakarta-tomcat-connectors configuration problem.

-- 
Jan-Henrik Haukeland

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to