Chris,
In tomcat 7.0.68 we added SSLv2Hello to allow our clients to connect but
that do not work in versions after that. Maybe they changed the meaning
of that protocol addition.
However, I changed the C++ POCO client to only use TLSv1.x and removed
the SSLv2Hello protocol from tomcat config.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 9/19/16 4:32 PM, Mark Thomas wrote:
> On 19/09/2016 21:20, Christopher Schultz wrote:
>> All,
>>
>> On 8/31/16 12:45 PM, Christopher Schultz wrote:
>>> All,
>>
>>> This isn't Tomcat-related, but many folks on this list have
>>> this kind
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
James,
On 9/8/16 4:48 PM, James H. H. Lampert wrote:
> On 9/8/16, 12:23 PM, Christopher Schultz wrote:
>
>> Would you care to create an account on the Tomcat Wiki[1] and
>> post your CL program? It may help someone else running in
>> similar enviro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thomas,
On 9/28/16 11:55 AM, Thomas Boniface wrote:
> Hi,
>
> When a client calls an asynchronous servlet and closes the
> connection a java.io.IOException: Broken pipe is catched by Tomcat
> level when the webapp tries to write to the socket.
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 9/28/16 2:21 PM, Mark Thomas wrote:
> On 28/09/2016 15:07, Berneburg, Cris J. - US wrote:
>> Chris
>>
>> -Original Message- From: Christopher Schultz
>> [mailto:ch...@christopherschultz.net] Sent: Saturday, September
>> 24, 2016 11
On 28/09/2016 15:07, Berneburg, Cris J. - US wrote:
> Chris
>
> -Original Message-
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Sent: Saturday, September 24, 2016 11:55 AM
> To: Tomcat Users List
> Subject: Re: JreMemoryLeakPreventionListener docs example
>
>> Once
Hi,
When a client calls an asynchronous servlet and closes the connection a
java.io.IOException: Broken pipe is catched by Tomcat level when the webapp
tries to write to the socket.
This exception is not transmited to the webapp level but it seems the
request has been recycled (all content is rei
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Magnus,
On 9/28/16 2:20 AM, Persson, Magnus (SE-TLX) wrote:
> The java servlet (in webapps folder) was written by a consultant
> and I have only looked at parts of the source code and don't know
> all that it does.
>
> The purpose is to give extern
Chris
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Saturday, September 24, 2016 11:55 AM
To: Tomcat Users List
Subject: Re: JreMemoryLeakPreventionListener docs example
> Once you are happy with your edits, do this:
While I can't say that "hap
Chris
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Saturday, September 24, 2016 11:55 AM
To: Tomcat Users List
Subject: Re: JreMemoryLeakPreventionListener docs example
[SNIP]
So, could we add a small example server.xml snippet to the
>>
Hi,
I really need to read up on https clients.
The referencec example written in python is using SSL23 and so did the
sample https client I wrote in c++ using POCO library. I found the
setting to switch to TSL1.x and now I can use tomcat 7.0.70 without
enabling the SSLv2Hello protocol.
Thanks
Dear all:
After updating Tomcat from 7.0.65 to 7.0.72, I can then use the Java 6 JCE
, use TLS 1.2 and 256 ciphers.
I just needed also to update Tomcat.
Bottom line, if you are forced to stick with Tomcat 7 and Java 6, you can
still use TLS 1.2 and high ciphers by updating Java 6 and Tomcat 7 ma
12 matches
Mail list logo