James,
On Thu, Dec 26, 2019 at 4:49 PM James H. H. Lampert <
jam...@touchtonecorp.com> wrote:
> We have a Tomcat (8.5.40) server running on an Amazon EC2 instance,
> currently using a Java Keystore for the SSL support.
>
> We would like to be able to use Let's Encrypt, but I've learned that
>
You could use their public certificate with their lb and redirect 443 to
port 80 in the lb I was using jboss server running on port 80 in the ec2
instances that were running behind the lb. when I did that all requests
hitting the lb were secured. Jboss is another container like tomcat.
Hope
Dear Olaf
Thank you so much for your reply.
*problem: You're trying to deliver the HSTS header for some, but not allof
the requests coming in(?) (Otherwise, please correct) *
- > No. I want to respond HSTS header in all request but after I follow
configuration below it not response HSTS header
We have a Tomcat (8.5.40) server running on an Amazon EC2 instance,
currently using a Java Keystore for the SSL support.
We would like to be able to use Let's Encrypt, but I've learned that
Let's Encrypt and Tomcat don't get along all that well together. The
best I've found so far are article
Hi Mark,
I just recently tested Step CA (smallstep.com) as an internal CA that provides
an internal ACME service.
After I deployed the created cert to my Tomcat (8.5.50 with adoptopenjdk 11) I
noticed that while the openssl connector immediately started, the JSSE
connector with the same cert
On 26.12.19 11:22, Pattavee Sanchol wrote:
> Dear support team
>
> I config tomcat server to enabled HSTS some request URI path not
> response with Secure heading
>
> ...
>
>
> I some request URI such as http://192.168.1.1/%20 is not response with
> security hedering
>
>
> this is working
>
>
>
Dear support team
I config tomcat server to enabled HSTS some request URI path not response
with Secure heading
The configuration illustrated below
httpHeaderSecurity
org.apache.catalina.filters.HttpHeaderSecurityFilter
true
hstsEnabled
true
