[CONF] Apache Tomcat > Servlet TCK 5.0 (DRAFT)

[Apache Software Foundation]

Title: Message Title

There's 2 new comments and 1 new edit on this page

Servlet TCK 5.0 (DRAFT) 2 new comments Olivier Lamy Error page attributes maybe related to https://github.com/eclipse-ee4j/jakartaee-tck/pull/277  View comment • Reply • Like Mark Thomas Looks like it. That at least explains how the test passed previously. I was wondering. View comment • Reply • Like 1 new edit Mark Thomas edited this page Here's what changed: ...    <CookieProcessor className="org.apache.tomcat.util.http.LegacyCookieProcessor" alwaysAddExpires="true" forwardSlashIsSeparator="false" /> ... </Context> server.xml Enable h2c on port 8080, and add some trailer headers <Connector ... allowedTrailerHeaders="myTrailer, myTrailer2" > ... Tomcat config for Servlet 4.0 setenv.[sh|bat] Set the following system properties ... ... server.xml Enable h2c on port 8080, and add some trailer headers <Connector ... allowedTrailerHeaders="myTrailer, myTrailer2"> ... </Connector> Enable TLS on port 8443     <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"> ... A default 10.0.x build (as of 2020-06-18) with the above configuration and the TCK built from source (as of 2020-06-18) triggers 32 25 test failures 1 Expected failures ... PR 338 Incorrect major version (1 failure), Using LF rather an CRLF (15 failures) Strange /j_security_check test (2 failures) Error page attributes assumed to be unset when spec requires them to be set (3 failures) Missing annotation marker in Java 8 signature tests (1 failure) 10 2 failures suspected to be related to incomplete configuration or additional TCK bugsclient-cert configuration. Signature tests with Java 11 not yet tested. Go to page history View page

Stop watching space • Manage notifications This message was sent by Atlassian Confluence 7.5.0