Re: AW: AW: AJP Connector issue

2020-03-20 Thread Christopher Schultz
a va > > :274) >>>>> at >>>>> > org.apache.catalina.connector.Connector.startInternal(Connector.java:1 05 > > 5) >>>>> ... 12 more >>>>> >>>>> This new "secretRequired" attribute prevents the To

Re: AW: AW: AJP Connector issue

2020-03-20 Thread Christopher Schultz
m of the message and start typing instead of typing at the top :) - -chris > -Original Message- From: Christopher Schultz > Sent: Friday, March 20, 2020 11:40 > AM To: users@tomcat.apache.org Subject: Re: AW: AW: AJP Connector > issue > > RK, > > On 3/20/20 09:57, RK

Re: AW: AW: AJP Connector issue

2020-03-20 Thread RK Ashburn
> >> This new "secretRequired" attribute prevents the Tomcat from > >> starting flawlessly. It was first introduced with the Ghostcat > >> release. So this is a wish from me to the Tomcat developers: > >> Please set this new attribute not mandat

RE: AW: AW: AJP Connector issue

2020-03-20 Thread jonmcalexander
Please set this new attribute not mandatory but optional. So that I >> can run the newest Tomcat >> without this attribute which I do now with the pre-Ghostcat releases. >> >> Have a nice weekend Florian Fritze >> >> -- Florian Fritze M.A. Fraunhofer-Informations

Re: AW: AW: AJP Connector issue

2020-03-20 Thread Christopher Schultz
not mandatory but optional. So that >> I can run the newest Tomcat >> without this attribute which I do now with the pre-Ghostcat >> releases. >> >> Have a nice weekend Florian Fritze >> >> -- Florian Fritze M.A. Fraunhofer-Informationszentrum Raum und

Re: AW: AW: AJP Connector issue

2020-03-20 Thread RK Ashburn
-- > Florian Fritze M.A. > Fraunhofer-Informationszentrum Raum und Bau IRB > Competence Center Research Services & Open Science > Nobelstr. 12, 70569 Stuttgart, Germany > Telefon +49 711 970-2713 > florian.fri...@irb.fraunhofer.de | www.irb.fraunhofer.de > > > -Ursprüngliche Nac

Re: AW: AW: AJP Connector issue

2020-03-20 Thread tomcat/perl
Ok, so it looks like : - the request is effectively reaching tomcat, and that it is tomcat sending back the 403 response. - the URL is "/", so presumably it is "well-formed" etc. Furthermore, according to something you wrote below, both Apache httpd and tomcat are running on the same Linux hos