Hi folks,
has anymore ever used Tomcat behind mod_proxy_http where a client does a
PUT/POST with "Expect: 100-continue"?
I recently started using Tomat 8.5.31 behind HTTPd 2.4.33 and
immediately hit BZ 60330/55433. HTTPd responds with HTTP/1.1 100 instead
of receiving this from Tomcat. The outcome is that the client uploads
its data twice because Tomcat challenges the client to authenticate
whereas HTTPd does not of course. I know that Tomcat does everything
correctly because a direct connection works as expected.
Is there any remedy to this? I will try mod_proxy_ajp tomorrow. If no
solution is available, this will basically mean that I have to drop
HTTPd proxying the requests and lose potential balancing features in the
future for this service.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
