What's wrong with the Content-Location: https://www.dowearysoftware.com:443/index.jsp ?
What would you expect to see in a correct Content-Location?
Can you give me some insight as to how I might reconfigure my IIS/jakarta-tomcat-connectors to correct this problem?


I know that the Content-Length on the server certificate that I created was only 1024K, and your message below shows a Content-Length of 5575K Could this have something to do with my problem? Do I need to create a server certificate that can handle a Content-Length of 5575K?

I will also change the Content-Type to Text/HTML.



From: Jan-Henrik Haukeland <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
Subject: Re: HTTPS problem - Jsp pages no working with IIS 6.0 SSL.
Date: Tue, 27 Jan 2004 14:21:28 +0100

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

_________________________________________________________________
Find high-speed �net deals � comparison-shop your local providers here. https://broadband.msn.com



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



Reply via email to