Truncated response via mod

This is a multi-part message in MIME format.

------_=_NextPart_001_01C918E8.529F8198
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I'm trying to debug an issue with a client getting a truncated response
via mod_proxy and mod_ssl on apache 2.0.63. The client software is
SQLAnywhere, and they are trying to get a response from a backend web
service running under IIS6. If they make the request directly against
the origin server via SSL or port 80, it works. If they query via the
reverse-proxy on port 80, it works. On SSL via the reverse-proxy the
results are truncated (only part of the XML is returned).

This reverse-proxy serves hundreds of vhosts and thousands of clients a
day. This is the only vhost + client with a problem.

Using wireshark, we can see that the rproxy is sending an encrypted
alert 21 and then client is sending an SSL alert 21 and closing the
connection.

I've set Apache's LogLevel to debug, and I can see the incoming SSL
handshake and the request, and I can see the mod_proxy working, but I
don't see a detailed trace of the response going back (even though a
partial response is sent). The access log says that the whole response
is returned. Is there some special command to trace the response?

Regards,

Ryan

------_=_NextPart_001_01C918E8.529F8198
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>

</style>

</head>

<body lang=3DEN-CA link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

I’m trying to debug an issue with a client =
getting a
truncated response via mod_proxy and mod_ssl on apache 2.0.63. The =
client
software is SQLAnywhere, and they are trying to get a response from a =
backend
web service running under IIS6. If they make the request directly =
against the
origin server via SSL or port 80, it works. If they query via the =
reverse-proxy
on port 80, it works. On SSL via the reverse-proxy the results are =
truncated
(only part of the XML is returned).<o:p></o:p>

<o:p> </o:p>

This reverse-proxy serves hundreds of vhosts and =
thousands
of clients a day. This is the only vhost + client with a =
problem.<o:p></o:p>

<o:p> </o:p>

Using wireshark, we can see that the rproxy is =
sending an
encrypted alert 21 and then client is sending an SSL alert 21 and =
closing the
connection. <o:p></o:p>

<o:p> </o:p>

I’ve set Apache’s LogLevel to debug, and =
I can
see the incoming SSL handshake and the request, and I can see the =
mod_proxy
working, but I don’t see a detailed trace of the response going =
back
(even though a partial response is sent). The access log says that the =
whole
response is returned. Is there some special command to trace the =
response?<o:p></o:p>

<o:p> </o:p>

Regards,<o:p></o:p>

<o:p> </o:p>

Ryan<o:p></o:p>

<o:p> </o:p>

</div>

</body>

</html>

------_=_NextPart_001_01C918E8.529F8198--
____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users [at] modssl.org
Automated List Manager majordomo [at] modssl.org

Truncated response via mod_proxy