This was a typo, no plans for tls 1.3 in java yet
-Ursprüngliche Nachricht-
Von: Christopher Schultz [mailto:ch...@christopherschultz.net]
Gesendet: Donnerstag, 15. Dezember 2016 22:36
An: Tomcat Users List
Betreff: Re: Tomcat Version 7.0.34 + jdk 1.6 is not supporting TLS Protocol
TLS1
It's correct that Java7 is sufficient for tls1.2 but to be more secure and use
recent cipher suits I recommend use java8 which is the only maintained version
by Oracle
> Am 15.12.2016 um 16:55 schrieb Hrivnak, Dan :
>
>
>
> On 12/15/16, 9:19 AM, "frank.pien...@materna.de"
> wrote:
>
>
>
Q1 use recent java8 Version if you want secure TLS 1.3 choose right cipher.
https://wiki.apache.org/tomcat/Security/Ciphers
q2
Jre8u122+Tomcat 7.0.73
Q3 Upgrade should be easy and you need it for Tls1.2
Question 1. DO we need to upgrade Tomcat Version and Java Version, if yes
which version we ne
Try start Tomcat with strict compliance enabled. Add the following to your
startup script.
-Dorg.apache.catalina.STRICT_SERVLET_COMPLIANCE=true
When STRICT_SERVLET_COMPLIANCE is set to true, Tomcat will always send an HTTP
Content-type header when responding to requests. This is significant as
Hi there
The Apache Tomcat Maven Plugin supports only Apache Tomcat/7.0.47.
http://tomcat.apache.org/maven-plugin-trunk/
Does anybody know if a Tomcat8.5 support is planned or has an alternative eg.
build an own launcher main class
Thanks for reply
Frank
OK Rainer i moved log4j-core-2.6.2.jar, log4j-api-2.6.2.jar,
log4j-jul-2.6.2.jar and log4j2.xml to $CATALINA_HOME/bin
Then changed
set
JAVA_OPTS=-Djava.util.logging.manager=org.apache.logging.log4j.jul.LogManager
set LOGGING_CONFIG=-DnoOpp
set
LOGGING_MANAGER=-Djava.util.logging.manager=org.apac
It's a little bit frustrating to configure Tomcat 8.5.8 with log4j2.
I put the following jars in $CATALINA_HOME/lib
log4j 2 core (log4j-core-2.6.2.jar)
log4j 2 api (log4j-api-2.6.2.jar)
Delete the file $CATALINA_HOME/conf/logging.properties
Put the new log4j 2 config file (log4j
