I got slightly confused with the error message "command" because where I
come from we use different terminology.
Element
Description
http://localhost:8080 The
web server to process the request
/manager/text
The name and location of server resource
?
Something else I noticed, just now:
If I do an "ss -tulwn" on the EC2 instance under discussion, it only
lists 8443, not 443. And yet if I look at the AWS management console,
the security group I set up allows 443, but not 8443, and I don't see
anything external to the box that would be doing t
As it happens, one way or another (and I'm not entirely sure
*which* way; I'd have to look at my notes), we *do* have Tomcat
listening directly on 443 (but not 80; nothing there is currently
listening on 80) on that particular EC2 instance (and I'm pretty
sure we have HTTPD running on a *different
Hi All,
If possible, I think it's better to let 443 (https) requests hitting an
instance be redirected to 80 so you don't have to configure an SSL locally
in the instance itself. It's very cumbersome to do it that way.
You can also use a single instance behind an AWS LB if you only have one
inst
As it happens, one way or another (and I'm not entirely sure
*which* way; I'd have to look at my notes), we *do* have Tomcat
listening directly on 443 (but not 80; nothing there is currently
listening on 80) on that particular EC2 instance (and I'm pretty
sure we have HTTPD running on a *different
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
James,
On 12/27/19 14:22, James H. H. Lampert wrote:
> On 12/26/19 8:31 PM, Igal Sapir wrote:
>> You should check out Chris' presentations on the topic. He
>> outlines a very efficient process. There is probably more
>> materials out there, but a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Peter,
On 12/27/19 11:27, logo wrote:
> Am 2019-12-27 16:40, schrieb Christopher Schultz: That's the plan.
> In Las Vegas, Christopher Tubbs did say to me "aw, I was really
> hoping for you to tell us that you just set letsEncrypt="true" in
> your c
On 12/26/19 8:31 PM, Igal Sapir wrote:
You should check out Chris' presentations on the topic. He outlines a very
efficient process. There is probably more materials out there, but a quick
search brings up the video [1] and slides [2] from his presentation at
ApacheCon earlier this year, as wel
Chris
Am 2019-12-27 16:33, schrieb Christopher Schultz:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Peter,
On 12/26/19 18:55, logo wrote:
Hi Mark,
I hope it's okay if I reply. :)
:-)
I just recently tested Step CA (smallstep.com) as an internal CA
that provides an internal ACME s
Chris,
Am 2019-12-27 16:40, schrieb Christopher Schultz:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Peter,
On 12/27/19 07:24, logo wrote:
Hi James,
Am 2019-12-27 05:31, schrieb Igal Sapir:
James,
On Thu, Dec 26, 2019 at 4:49 PM James H. H. Lampert <
jam...@touchtonecorp.com> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Pattavee,
On 12/26/19 05:22, Pattavee Sanchol wrote:
> Dear support team
>
> I config tomcat server to enabled HSTS some request URI path not
> response with Secure heading
>
> The configuration illustrated below
>
>
>
> httpHeaderSecurity
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alex,
On 12/27/19 10:07, Alex O'Ree wrote:
> i use letsencrypt with tomcat. i adopted a cronjob/bash script that
> auto renews the cert before expiration, it then stops tomcat,
> refreshes the jks files, then restarts tomcat. yeah it's down time,
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Peter,
On 12/27/19 07:24, logo wrote:
> Hi James,
>
> Am 2019-12-27 05:31, schrieb Igal Sapir:
>> 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 runn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Peter,
On 12/26/19 18:55, logo wrote:
> Hi Mark,
I hope it's okay if I reply. :)
> 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.
Good, please expand
On Fri, 27 Dec 2019, 15:27 Christopher Schultz, <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Zahid,
>
> On 12/23/19 15:19, Zahid Rahman wrote:
> > If your backend tomcat servers are running on different physical
> > machines t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Giancarlo,
On 12/23/19 12:45, Giancarlo Celli wrote:
> Hi, I need to configure a load balancer with apache connector on a
> jelastic server that redirects requests to 6 server workers with
> tomcat 7 installed. Atteched you can find extract from htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Zahid,
On 12/23/19 15:19, Zahid Rahman wrote:
> If your backend tomcat servers are running on different physical
> machines therefore with different ip addresses then there is
> nothing wrong with each backend tomcat server listening on same
> port
i use letsencrypt with tomcat. i adopted a cronjob/bash script that auto
renews the cert before expiration, it then stops tomcat, refreshes the jks
files, then restarts tomcat. yeah it's down time, but it is minimal and it
works
On Thu, Dec 26, 2019 at 7:49 PM James H. H. Lampert <
jam...@touchton
Hi James,
Am 2019-12-27 05:31, schrieb Igal Sapir:
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 t
19 matches
Mail list logo
