On 06/03/2020 06:46, Thomas Glanzmann wrote:
> the issue seems to be that mod_jk no longer works without a password
> with tomcat7. So you need to set a password on both sites, and than
> everything works again.
This is not the case. Tomcat can be configured so a secret is not required.
> serv
Hello,
> If you don't set secretRequired="false" properly then at start time Tomcat
> will complain if there is no specified "secret" attribute.
> If it doesn't complain then most probably you are testing again with the
> wrong server.xml or old version of Tomcat.
the issue seems to be that mod_j
On Thu, Mar 5, 2020 at 10:05 AM Thomas Glanzmann
wrote:
> Hello Martin,
>
> > > This should be: secretRequired="false".
> > > This attribute has been renamed recently.
>
> I just looked at my notes, and I tried that already yesterday night.
> Still facing the same problem with 403. Might it be po
Hello Martin,
> > This should be: secretRequired="false".
> > This attribute has been renamed recently.
I just looked at my notes, and I tried that already yesterday night.
Still facing the same problem with 403. Might it be possible that I need
to use a secret in order to access ajp from mod_jk?
Hello Martin,
> This should be: secretRequired="false".
> This attribute has been renamed recently.
thanks. I'll test later and let you know how it went.
Cheers,
Thomas
-
To unsubscribe, e-mail: users-unsubscr...@tomcat
Hi Thomas,
On Thu, Mar 5, 2020 at 3:53 AM Thomas Glanzmann wrote:
> Hello,
> the problem was that I edited the wrong server.xml. The one that was not
> used. So now that I figured that out, settings these two settings help.
>
>
>
>
> className="org.apache.catalina.core.JreMem
Hello,
the problem was that I edited the wrong server.xml. The one that was not
used. So now that I figured that out, settings these two settings help.