Truncated response via mod_proxy

am 17.09.2008 19:10:45 von Ryan.Kogelheide

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).

=20

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

=20

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.=20

=20

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?

=20

Regards,

=20

Ryan

=20

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

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

charset=3Dus-ascii">

style=3D'font-size:10.0pt;
font-family:Arial'>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).

style=3D'font-size:10.0pt;
font-family:Arial'>

style=3D'font-size:10.0pt;
font-family:Arial'>This reverse-proxy serves hundreds of vhosts and =
thousands
of clients a day. This is the only vhost + client with a =
problem.

style=3D'font-size:10.0pt;
font-family:Arial'>

style=3D'font-size:10.0pt;
font-family:Arial'>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.

style=3D'font-size:10.0pt;
font-family:Arial'>

style=3D'font-size:10.0pt;
font-family:Arial'>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?

style=3D'font-size:10.0pt;
font-family:Arial'>

style=3D'font-size:10.0pt;
font-family:Arial'>Regards,

style=3D'font-size:10.0pt;
font-family:Arial'>

style=3D'font-size:10.0pt;
font-family:Arial'>Ryan

style=3D'font-size:
12.0pt'>

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