After digging through the source code of isapi_redirect.dll, I've discovered
the following:
1. Transfer-Encoding isn't a supported header entry. Chunked data isn't
preserved as chunked data.
2. I still don't know why the content-length of "dechunked" data isn't
getting stored in the response header.
2. isap_redirect doesn't support messages larger than 8K.
Are any of these issues scheduled to be address in the next release?
My intent was to integrate with IIS in order to be able to restrict access
to a fixed set of IP addresses. Due to the above limitations, I need to
look for another solution. Is there any way to do this in standalone
Tomcat?
Rida
-----Original Message-----
From: Rida Ligurs
Sent: Monday, January 21, 2002 11:52 AM
To: Tomcat-User (E-mail)
Subject: Does isapi_redirect support chunked data?
I have a servlet that returns a SOAP document in its output stream.
I have a Java client that posts a request using sockets and expects to read
the response (SOAP document) from the socket's input stream.
Everything works fine if I'm posting directly to Tomcat. I get the
following data from the input stream:
HTTP/1.1 200 OK
Content-Type:text/xml
Date:Mon, 21 Jan 2002 15:19:54 GMT
Transfer-Encoding:chunked
Server:Apache Tomcat/4.0.1 (HTTP/1.1 Connector)
44 // chunk size
<SOAP data chunk>
23 // chunk size.
<SOAP data chunk>
0
But when I post to IIS running with isapi_redirect, the input stream
contains the following:
HTTP/1.1 200 OK
Server:Microsoft-IIS/5.0
Date:Mon, 21 Jan 2002 15:25:54 GMT
Connection:Close
Content-Type:text/xml
<SOAP data>
Is chunked data supposed to get handled this way?
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
