Re: Problems with Http11NioProtocol and proxy server

[Luca Toscano <toscano.luca@xxxxxxxxx>]

Hi Marco,

2017-08-29 11:07 GMT+02:00 <bulau@xxxxxxxxx>:

Hi,

we've build a web application with JSF 2.1 and RichFaces 4.5.13.Final running on JBoss EAP 6.4.12. We're also using a Apache HTTP server 2.4.7 as a HTTPS/WSS proxy to access the application for customers.

After we've changed the EAP http connector to "org.apache.coyote.http11.Http11NioProtocol" (for using websockets/push), ajax requests are often answered by HTTP 400 (Bad Request) or HTTP 500 (Bad Gateway).

We're switched back to the EAP http connector "HTTP/1.1" and everything is working again as expected.

If we're accessing the EAP directly (not via proxy) there is also no problem. It looks like that there is a problem using Http11NioProtocol with Apache HTTP server as a proxy.

Is there anyone who run into the same problem or has an idea how we can solove it? 

We'd need to know a couple of things to help:

1) Is there any specific error in the httpd error_log that gets logged when the 400/500s are returned?

2) What kind of requests are you issuing to httpd when you get a 400 and a 500? Are they different?

3) Can you share your configuration? (at least the one for the proxy)

4) Do you find anything useful in the Tomcat logs when httpd returns the errors?

Luca