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
All,
I'm sorry for using users@ as my own personal Google but I'm sure
someone knows this off the top of their head and can save me a lot of
reading.
I'm wondering about which specs mention how to handle URL parameters
(and POST parameters, for that matter) in terms of ordering. For
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
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
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,
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
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
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
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:
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
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
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
Hi Leo,
why would you want to do that if you could do the same with Java? What is the
motivation, the use
case for you?
How urgent is this (I may have something for both, Java EE and Jakarta EE, but
need a little bit of
time)?
—-rony
On 15.02.2021 07:29, leo wrote:
> Hi there
>
> I am
14 matches
Mail list logo
