-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Garret,
On 2/8/19 08:27, Garret Wilson wrote:
> On 2/7/2019 9:54 PM, Christopher Schultz wrote:
>> … I would argue that adding Apache httpd into the mix (where is
>> it not already there) is more complicated than using Let's
>> Encrypt with Tomcat.
On 2/7/2019 9:54 PM, Christopher Schultz wrote:
…
I would argue that adding Apache httpd into the mix (where is it not
already there) is more complicated than using Let's Encrypt with
Tomcat.
OK, I guess I didn't figure in the part about adding/configuring the
connector. But still there are a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Garret,
On 2/7/19 12:22, Garret Wilson wrote:
> On 2/7/2019 3:13 PM, Christopher Schultz wrote:
>> … Have a look at this presentation:
>> https://people.apache.org/~schultz/ApacheCon%20NA%202018/Let's%20Encr
ypt
>>
>>
%20Apache%20Tomcat.pdf
>
> T
On 2/7/2019 3:13 PM, Christopher Schultz wrote:
…
Have a look at this presentation:
https://people.apache.org/~schultz/ApacheCon%20NA%202018/Let's%20Encrypt
%20Apache%20Tomcat.pdf
The presentation gets two thumbs up, specifically:
* Great corny grammar ambiguity joke on the title page.
* The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Garret,
On 2/7/19 11:45, Garret Wilson wrote:
> Hi, everyone. In the computer course I'm writing I'm using Tomcat
> for the server. (Students learn how to set up CentOS and everything
> from scratch. Currently the course has them using Tomcat runnin
You can use apache with mod_jk and then just setup the ssl through apache
and tomcat will use the 443 port through apache.
If you want to use letencrypt you need to add JkUnMount for /.well-known/*
directory so that when you run lets encrypt it can create and get to this
directory through apache.
