Hello Richard/Friends,
I might be wrong, but I guess the best approach would be to use apache
httpd or nginx as a reverse proxy and leave tomcat alone
Kind Regards,
Geraldo Netto
Sapere Aude => Non dvcor, dvco
http://exdev.sf.net/
On Sun, 25 Nov 2018 at 00:05, wrote:
>
> Tomcat/9.0.13
>
>
> I
Tomcat/9.0.13
I'd like to have my webapps generally on 443, but the manager and
host-manager on some other port, say 444.
My reason for doing that would be that I could then use linux's iptables
to restrict access to 444 to a few known addresses, but anyone could
access 443.
I would of co
Here is what I see
Loaded Modules:
core_module (static)
so_module (static)
http_module (static)
access_compat_module (shared)
actions_module (shared)
alias_module (shared)
allowmethods_module (shared)
auth_basic_module (shared)
auth_digest_module (shared)
authn_anon_module (shared)
auth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Lou,
On 11/24/18 12:19, Lou Wallace wrote:
> Hi Greg,
>
> I did this and restarted HTTPD. No error but no change.
>
> Not sure how 10-my.conf and my.conf are called, but I did create
> them as described.
>
> Also when I checked configtest
>
> [r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Esther,
On 11/24/18 14:48, Esther Montes wrote:
> Disculpe pero es q no le entiendo
Lo siento si no me entiendes El idioma oficial de esta lista de correo
es el inglés. Si lo desea, puede unirse a una lista de correo
diferente si desea utilizar el
Disculpe pero es q no le entiendo
El sáb., 24 de nov. de 2018 8:13 AM, Christopher Schultz <
ch...@christopherschultz.net> escribió:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Tim,
>
> On 11/23/18 12:55, Christopher Schultz wrote:
> > Okay, the problem is that I built the EncryptInte
Hi Greg,
I did this and restarted HTTPD. No error but no change.
Not sure how 10-my.conf and my.conf are called, but I did create them as
described.
Also when I checked configtest
[root@server2 conf]# apachectl configtest
Syntax OK
and apachectl -S
[root@server2 conf]# apachectl -S
VirtualHos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Gilles,
On 11/23/18 05:07, Gilles SCHLIENGER wrote:
> Thanks Mark for your answer
>
> Here is what I found in case someone has the same problem.
>
> When you use parallel deployment, you should not use a connexion
> pool in the context.xml file
W
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Tim,
On 11/23/18 12:55, Christopher Schultz wrote:
> Okay, the problem is that I built the EncryptInterceptor without
> realizing that cluster-messaging isn't single-threaded. It's
> completely non-thread-safe and it needs to be.
>
> There is a s
Le vendredi 23 novembre 2018 à 23:51 +0100, Rémy Maucherat a écrit :
> On Wed, Nov 21, 2018 at 10:58 AM Mark Thomas
> wrote:
>
> > - French has increased from 18% to 64% coverage
> >
>
> Done (well, close enough, a few tribes/ha remain) !
A single translation remains to be performed.
Jump to h
On Sat, Nov 24, 2018 at 12:01 AM Mark Thomas wrote:
> On 23/11/2018 22:51, Rémy Maucherat wrote:
> > On Wed, Nov 21, 2018 at 10:58 AM Mark Thomas wrote:
> >
> >> - French has increased from 18% to 64% coverage
> >>
> >
> > Done (well, close enough, a few tribes/ha remain) !
> >
> > Or rather, th
11 matches
Mail list logo
