Skip to main content

Hello,
Our architecture has a loadbalancer that checks Uniface by sending a HTTP 1.0 request on the main page of our application.

It was working fine till Uniface 10.3.03/Tomcat 8.5. When switching to 10.4.02/Tomcat 9.0, Tomcat does  not accept the connexion (Error 400 in the logs).
This is on a https connexion.
Does anyone know whether we can get Tomcat 9.0 to accept HTTP 1.0 ? Is there a setup somewhere that would allow it ?

So far our connexion string in server.xml looks like:
<Connector port="8090" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="8091" />
<Connector port="8091" maxThreads="150" scheme="https" secure="true" SSLEnabled="true"
keystoreFile="conf/AVMEUPMCAPP01-02.p12" keystorePass="*****"
clientAuth="false" keyAlias="tomcat" sslProtocol="TLS"/>
It has not been the change during the migration.

When we access the server directly through a browser, it works fine.

Thanks,

Stephane



------------------------------
Stephane Pfefer
Application Specialist
Darling
------------------------------

Hello,
Our architecture has a loadbalancer that checks Uniface by sending a HTTP 1.0 request on the main page of our application.

It was working fine till Uniface 10.3.03/Tomcat 8.5. When switching to 10.4.02/Tomcat 9.0, Tomcat does  not accept the connexion (Error 400 in the logs).
This is on a https connexion.
Does anyone know whether we can get Tomcat 9.0 to accept HTTP 1.0 ? Is there a setup somewhere that would allow it ?

So far our connexion string in server.xml looks like:
<Connector port="8090" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="8091" />
<Connector port="8091" maxThreads="150" scheme="https" secure="true" SSLEnabled="true"
keystoreFile="conf/AVMEUPMCAPP01-02.p12" keystorePass="*****"
clientAuth="false" keyAlias="tomcat" sslProtocol="TLS"/>
It has not been the change during the migration.

When we access the server directly through a browser, it works fine.

Thanks,

Stephane



------------------------------
Stephane Pfefer
Application Specialist
Darling
------------------------------

This issue has been solved. The loadbalancer had a wrong setting int the custom header.

Tomcat 8.5 did not mind about a header that does not comply with the norm; however Tomcat 9.0 is not so much forgiving and that was leading to reject the request.

The loadbalancer header has been corrected and it works now as expected.



------------------------------
Stephane Pfefer
Application Specialist
Darling
------------------------------

This issue has been solved. The loadbalancer had a wrong setting int the custom header.

Tomcat 8.5 did not mind about a header that does not comply with the norm; however Tomcat 9.0 is not so much forgiving and that was leading to reject the request.

The loadbalancer header has been corrected and it works now as expected.



------------------------------
Stephane Pfefer
Application Specialist
Darling
------------------------------
Thanks for letting us know. It is good to hear that you could resolve this problem in the meantime.

------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland
------------------------------