Closed fkleedorfer closed 5 years ago
So the tomcat's server.xml schema has changed. tomcat 8.5 needs this Connector
config:
<Connector
port="8443"
protocol="org.apache.coyote.http11.Http11AprProtocol"
SSLEnabled="true"
maxThreads="200"
compressibleMimeType="text/html, text/xml, text/plain, text/css, text/javascript, application/javascript, application/x-font-ttf, image/svg+xml, text/turtle, application/rdf+xml, application/x-turtle, text/rdf+n3, application/json, application/trig, application/ld+json, application/n-quads"
compression="on"
disableUploadTimeout="true"
enableLookups="true"
maxPostSize="5242880000"
maxSpareThreads="75"
minSpareThreads="5"
scheme="https"
secure="true">
<SSLHostConfig
certificateVerification="optionalNoCA"
certificateVerificationDepth="2"
protocols="all">
<Certificate certificateKeyFile="c:/DATA/DEV/workspace/webofneeds/webofneeds/certs/won-server-certs/t-key.pem"
certificateFile="c:/DATA/DEV/workspace/webofneeds/webofneeds/certs/won-server-certs/t-cert.pem"
certificateKeyPassword="changeit"/>
</SSLHostConfig>
<UpgradeProtocol className="org.apache.coyote.http2.Http2Protocol" />
</Connector>
The nice thing about this bug is that now we can use tomcat 8.5 and HTTP/2.0. I'll have a look at tomcat 9.0 now and then update the config and possibly also the tomcat docker containers
The setup guide works for tomcat 8.0.x, but that version has reached end of life.
If you try it with tomcat 8.5.x, it seems the server does not ask for a client certificate, so the client does not send one, which then causes the following exception on the node (server):
The client (owner) logs the following exception: