Hi,
Tomcat server started successfully.
I'm seeing the following error in the tomcat logs when SSL is enabled in
server.xml
Application is not able to run on https://localhost:8080.
2022-06-15 12:02:43,923 [http-3003-1] DEBUG
*org.apache.tomcat.util.net.JIoEndpoint
- Handshake failed*
*javax.n
Hello Christopher,
> -Ursprüngliche Nachricht-
> Von: Christopher Schultz
> Gesendet: Dienstag, 14. Juni 2022 20:26
> An: users@tomcat.apache.org
> Betreff: Re: Filehandle left open when using sendfile
>
> Thomas,
>
> On 6/14/22 13:52, Thomas Hoffmann (Speed4Trade GmbH) wrote:
> > Hello
The Apache Tomcat team announces the immediate availability of Apache
Tomcat Native 1.2.34 stable.
The key features of this release are:
- Refactor the initialization of the native code so it is compatible
with Tomcat 10.1.x where deprecated Java classes will be removed
- Map the OpenSSL 3.0.
On 6/14/22 13:06, Christopher Schultz wrote:
Thanks so much for your perseverance.
On 6/14/22 14:43, Rob Sargent wrote:
Let's get one thing working at a time. I reviewed this thread, and I
honestly can't figure out exactly what you are trying to do. Can you
please clarify?
1. "I want to
Rob,
On 6/14/22 14:43, Rob Sargent wrote:
I have my environment working again but not with supplying both keystore
and truststore to both the server and the client. Clearly scrogged
somewhere
Let's get one thing working at a time. I reviewed this thread, and I
honestly can't figure out exac
On 6/14/22 12:43, Rob Sargent wrote:
On 6/2/22 16:06, Rob Sargent wrote:
I'm starting both the server and the client with both key and
trust. Does that bite?
I would avoid giving access to the key to anything that doesn't
absolutely need it. Usually, only the server needs access to the
On 6/2/22 16:06, Rob Sargent wrote:
I'm starting both the server and the client with both key and trust.
Does that bite?
I would avoid giving access to the key to anything that doesn't
absolutely need it. Usually, only the server needs access to the key.
-chris
-
Thomas,
On 6/14/22 13:52, Thomas Hoffmann (Speed4Trade GmbH) wrote:
Hello,
we are using Tomcat 10.0.16 under windows.
For sending files to the browser, we are using sendfile by setting the attribute
"org.apache.tomcat.sendfile.filename".
Streaming an image to the browser works well in this way.
Hello,
we are using Tomcat 10.0.16 under windows.
For sending files to the browser, we are using sendfile by setting the
attribute "org.apache.tomcat.sendfile.filename".
Streaming an image to the browser works well in this way.
But we observed that if the user tries to delete the file afterwards,
Hello,
we are using Tomcat 10.0.16 under windows.
For sending files to the browser, we are using sendfile by setting the
attribute "org.apache.tomcat.sendfile.filename".
Streaming an image to the browser works well in this way.
But we observed that if the user tries to delete the file afterwards,
Pavan,
Please reply to the list and not me personally.
On 6/14/22 11:21, Pavan Kumar Tiruvaipati wrote:
acceptCount="100" scheme="https" secure="true"
connectionTimeout="2"
clientAuth="false" algorithm="SunX509" sslProtocol="TLS"
keystoreFile="conf/
Pavan,
On 6/14/22 08:32, Pavan Kumar Tiruvaipati wrote:
We have replaced JDK 1.8 with JRE 1.8.0_333.
SSL configuration was working fine with Tomcat 6.0.45 before replacing JDK
with JRE.
Now it's not working.
In server.xml, SSL Protocol is set to "TLS".
Does Tomcat 6.0.45 support SSL with JRE
Hi,
We have replaced JDK 1.8 with JRE 1.8.0_333.
SSL configuration was working fine with Tomcat 6.0.45 before replacing JDK
with JRE.
Now it's not working.
In server.xml, SSL Protocol is set to "TLS".
Does Tomcat 6.0.45 support SSL with JRE 1.8.0_333 ?
Are there any specific protocols / versi
13 matches
Mail list logo