-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Peter,
On 6/1/19 03:27, Peter Kreuser wrote:
> Crazy enough, but Google maps provides ciphers even for Java 6.
>
> https://www.ssllabs.com/ssltest/analyze.html?d=maps.google.com=216.5
8.195.78
>
> So this would be the only strange but obvious
What is your webapp using as HTTP client that handles the SSL?
-Original Message-
From: James Lampert
Sent: Friday, May 31, 2019 3:41 PM
To: Tomcat Users List
Subject: Re: AW: Outbound SSL?
This just keeps getting weirder and weirder.
I extracted the actual request
> ht
Tomcat can be setup in 2 modes =
JSSE (Java) or APR (OpenSSL)
If Java, turn Java debug log on and -Djavax.net.debug=ssl
> Sent: Wednesday, May 29, 2019 at 1:57 PM
> From: "James H. H. Lampert"
> To: "Tomcat Users List"
> Subject: Outbound SSL?
>
> We have
Chris, James
> Am 01.06.2019 um 02:30 schrieb Christopher Schultz
> :
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> James,
>
>> On 5/31/19 18:41, James H. H. Lampert wrote:
>>> On 5/31/19, 3:34 AM, bernd.sch...@daimler.com wrote:
>>> You can run a small java program on your jvm to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
James,
On 5/31/19 18:41, James H. H. Lampert wrote:
> On 5/31/19, 3:34 AM, bernd.sch...@daimler.com wrote:
>> You can run a small java program on your jvm to print out the
>> supported And default protocols. Yet, I didn’t find a better
>> way.
>>
On 5/31/19, 3:34 AM, bernd.sch...@daimler.com wrote:
You can run a small java program on your jvm to print out the supported
And default protocols.
Yet, I didn’t find a better way.
e.g. ==>
https://confluence.atlassian.com/stashkb/list-ciphers-used-by-jvm-679609085.html
If I set the same
This just keeps getting weirder and weirder.
I extracted the actual request
> https://maps.googleapis.com/maps/api/geocode/json?key==
from where it had been logged to catalina.out, and built a simple
program to feed it to Scott Klement's HTTPAPI, an open-source HTTP
interface for OS/400-native
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 5/31/19 13:50, André Warnier (tomcat) wrote:
> On 31.05.2019 18:12, James H. H. Lampert wrote:
>> Thanks.
>>
>> We think that the customer has solved the cipher problem,
>> because, at least as of when I checked on Wednesday, that error
On 31.05.2019 18:12, James H. H. Lampert wrote:
Thanks.
We think that the customer has solved the cipher problem, because, at least as
of when I
checked on Wednesday, that error message was no longer appearing.
Yet they're still not connecting. I can *ping* maps.googleapis.com from their
Thanks.
We think that the customer has solved the cipher problem, because, at
least as of when I checked on Wednesday, that error message was no
longer appearing.
Yet they're still not connecting. I can *ping* maps.googleapis.com from
their box, with no trouble whatsoever, But when the
Hi,
> -Ursprüngliche Nachricht-
> Von: Peter Kreuser
> Gesendet: Donnerstag, 30. Mai 2019 07:22
> Outbound SSL is usually handled by the underlying Java VM.
... and the problem occurs often if you use different jdks, like openjdk and
ibmjdk.
You can run a small java pro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Peter and James,
On 5/30/19 01:22, Peter Kreuser wrote:
> James,
>
> Outbound SSL is usually handled by the underlying Java VM.
Yep. Tomcat doesn't have any code to make outgoing TLS connections.
>> Am 29.05.2019 um 20:57 sch
James,
Outbound SSL is usually handled by the underlying Java VM.
> Am 29.05.2019 um 20:57 schrieb James H. H. Lampert :
>
> We have a customer that is running our Tomcat-based webapp, and it is
> apparently having trouble accessing a Google web service.
>
> The error messa
We have a customer that is running our Tomcat-based webapp, and it is
apparently having trouble accessing a Google web service.
The error message they're getting is:
Unable to find acceptable protocols. isFallback=false,
14 matches
Mail list logo
