https://bz.apache.org/bugzilla/show_bug.cgi?id=64762
--- Comment #11 from Ralf Hauser ---
The problem still persists, albeit we were able to almost make it disappear
We no longer wait a limited amount of sleep iterations, but "forever" (provided
the browser declares "content-length").
Reasoning:
Hi guys,
*Shortly*: Tomcat should have either Connector or SSLHostConfig option to
automatically reload certificate from the same file after X days, i.e.
reloadAfterDays=10 to force Tomcat to reload the certificate automatically
after 10 days.
*Long*:
SSL certificates have a period of expiration
Mladen,
On 12/19/20 05:12, Mladen Adamović wrote:
Hi guys,
*Shortly*: Tomcat should have either Connector or SSLHostConfig option to
automatically reload certificate from the same file after X days, i.e.
reloadAfterDays=10 to force Tomcat to reload the certificate automatically
after 10 days.
On Sat, Dec 19, 2020 at 2:29 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> Why not use cron? You can do this with a single "curl" command and the
> Manager+JMXProxyServlet.
>
We are not using Tomcat manager app.
Why someone should be forced to use Manager, to read/setup the
doc
https://github.com/apache/openwebbeans-meecrowave/tree/master/meecrowave-letsencrypt/src/main/java/org/apache/meecrowave/letencrypt
should be reusable just dropping the few references to meeceowave and
replacing it by valve or listener config in server.xml.
It sounds saner than a random reload N da
On Sat, Dec 19, 2020 at 4:25 PM Romain Manni-Bucau
wrote:
> It sounds saner than a random reload N days since it can reload when the
> cert changes.
>
Hi Romain,
BTW, Letsencrypt always creates a new file:
i.e.
lrwxrwxrwx 1 root root 35 Dec 1 01:05 cert.pem -> ../../archive/
numbeo.com/cert53.p
Le sam. 19 déc. 2020 à 16:43, Mladen Adamović a
écrit :
> On Sat, Dec 19, 2020 at 4:25 PM Romain Manni-Bucau
> wrote:
>
> > It sounds saner than a random reload N days since it can reload when the
> > cert changes.
> >
>
> Hi Romain,
> BTW, Letsencrypt always creates a new file:
> i.e.
> lrwxrwx
On Sat, Dec 19, 2020 at 5:06 PM Romain Manni-Bucau
wrote:
> Code can likely be simplified but high level it is just about enabling
> letsencrypt http dance thanks a valve and reloading the cert on update.
>
> Note that acme client is easy to recode to avoid any licensing work so it
> vould be a t
Le sam. 19 déc. 2020 à 17:34, Mladen Adamović a
écrit :
> On Sat, Dec 19, 2020 at 5:06 PM Romain Manni-Bucau
> wrote:
>
> > Code can likely be simplified but high level it is just about enabling
> > letsencrypt http dance thanks a valve and reloading the cert on update.
> >
> > Note that acme cl
Mladen,
On 12/19/20 11:33, Mladen Adamović wrote:
On Sat, Dec 19, 2020 at 5:06 PM Romain Manni-Bucau
wrote:
On a side note, Tomcat might be lacking a command line manager utility,
having manager running on a port sounds... like we are people who avoid a
command line, no?
There is a command-l
On Sat, Dec 19, 2020 at 6:30 PM Romain Manni-Bucau
wrote:
> It moves the problem elsewhere, how would the CLI communicate with tomcat?
> JMX, HTTP uses a port, a file based communication would be probably worse
> because of perms and other admin issues (and just not working in k8s).
>
I don't se
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
18 matches
Mail list logo
