Other than the browsers not trusting my self-signed cert I think I'm now
in the business of impersonation AWS ;)
Thanks to all I've bothered,
rjs
On 2/16/21 7:50 PM, Rob Sargent wrote:
Ah, yes, a stray Constuctor() left lying around.
Thank you! I am now down to dealing with https
Ah, yes, a stray Constuctor() left lying around.
Thank you! I am now down to dealing with https mis-configurations,
which puts me squarely back to the future.
Ever grateful,
rjs
On 2/16/21 3:27 PM, Mark Thomas wrote:
On February 16, 2021 10:00:01 PM UTC, Noelette Stout
wrote:
I'm kinda
On February 16, 2021 10:00:01 PM UTC, Noelette Stout
wrote:
>I'm kinda new to this, but it looks like you're trying to start http
>and
>https on the same port.
>
>Feb 16, 2021 1:06:59 PM org.apache.coyote.AbstractProtocol init
>INFO: Initializing ProtocolHandler ["http-nio-16004"]
>Feb
I'm kinda new to this, but it looks like you're trying to start http and
https on the same port.
Feb 16, 2021 1:06:59 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-nio-16004"]
Feb 16, 2021 1:06:59 PM org.apache.coyote.AbstractProtocol init
INFO:
change port assignment (16005) and restarted server. port in use.
On 2/16/21 2:36 PM, Rob Sargent wrote:
Rebooted desktop k1. I get port in use first time I start my server
(shell).
On 2/16/21 1:26 PM, Christopher Schultz wrote:
Rob,
On 2/16/21 15:02, Rob Sargent wrote:
The logging so
Rebooted desktop k1. I get port in use first time I start my server
(shell).
On 2/16/21 1:26 PM, Christopher Schultz wrote:
Rob,
On 2/16/21 15:02, Rob Sargent wrote:
The logging so far has told me only that my port 16004 is in use, but
at outset it clearly is not according to netstat or
Rob,
On 2/16/21 15:02, Rob Sargent wrote:
The logging so far has told me only that my port 16004 is in use, but at
outset it clearly is not according to netstat or ss. Is tomcat opening
that port before the call to "tomcat.start(); tomcat.getServer().await():"?
It it says "port in use" then
Sorry, meant to show the log:
Feb 16, 2021 1:06:59 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-nio-16004"]
Feb 16, 2021 1:06:59 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["https-jsse-nio-16004"]
Feb 16,
The logging so far has told me only that my port 16004 is in use, but at
outset it clearly is not according to netstat or ss. Is tomcat opening
that port before the call to "tomcat.start(); tomcat.getServer().await():"?
On 2/16/21 12:04 PM, Rob Sargent wrote:
I'm managed to open the flood
I'm managed to open the flood gates. Will report soon.
On 2/16/21 11:25 AM, Rob Sargent wrote:
Thanks, Chris,
Complete radio silence when running from command line [1][2] with a
startup script and running in IntelliJ [3]. (I wish I could make the
same /mistake/ with jOOQ;) ) I have managed
Thanks, Chris,
Complete radio silence when running from command line [1][2] with a
startup script and running in IntelliJ [3]. (I wish I could make the
same /mistake/ with jOOQ;) ) I have managed to get access-logging started.
The only warning I get (cmdline) is from the jvm
WARNING: An
Rob,
On 2/15/21 18:26, Rob Sargent wrote:
Thanks again, Chris,
On 2/15/21 1:32 PM, Christopher Schultz wrote:
Try this:
$ openssl s_client -showcerts -connect k1:16004 -tls1_2
openssl s_client -showcerts -connect k1:16004 -tls1_2
CONNECTED(0003)
140444510528832:error:1408F10B:SSL
I added a CORS filter to my /sgs/WEB-INF/web.xml. [1]
In hopes of getting some logs out of tomcat I have added a Valve to
/sgs/META-INF/context.xml [2]
Neither of these has had in affect. I see no logs and I still hit the
maybe-cors problem.
I have two tomcat connectivity checks: one is a
Thanks again, Chris,
On 2/15/21 1:32 PM, Christopher Schultz wrote:
Try this:
$ openssl s_client -showcerts -connect k1:16004 -tls1_2
openssl s_client -showcerts -connect k1:16004 -tls1_2
CONNECTED(0003)
140444510528832:error:1408F10B:SSL routines:ssl3_get_record:wrong
version
Rob,
On 2/15/21 13:41, Rob Sargent wrote:
openssl s_client -showcerts -connect k1:16004
CONNECTED(0003)
139674280387904:error:1408F10B:SSL routines:ssl3_get_record:wrong
version number:../ssl/record/ssl3_record.c:331:
---
no peer certificate available
---
No client certificate CA names
openssl s_client -showcerts -connect k1:16004
CONNECTED(0003)
139674280387904:error:1408F10B:SSL routines:ssl3_get_record:wrong
version number:../ssl/record/ssl3_record.c:331:
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 5 bytes and
mmm, I see...
- May I ask you to run ` openssl s_client -showcerts -connect
localhost:16004` to check that your tomcat connector has started? You
should get an output like `Verify return code: 18 (self signed certificate)`
- Having a look at what your browser is saying I have the feeling that
Luis,
Not a peep. Not in IntelliJ, nor from startup script (with zero output
redirects). It works (on localhost:16004 and on k1:16004 (fully
qualified), but only http, not https. The browser shows "This site
can’t provide a secure connection" and not much from chrome inspect:
request:
Hello Rob,
Do you have a stacktrace or error message that you can share?
Cheers,
Luis
El lun, 15 feb 2021 a las 1:26, Rob Sargent ()
escribió:
> Yep, me again.
>
> Inching along here, unable as yet to re-create ssl traffic when not on
> localhost. Moving from my basement (localhost) where
19 matches
Mail list logo
