Re: Version Question

Hi, On Sat, Mar 21, 2020, 00:37 wrote: > Good afternoon Mark and group. > > There is a question as to WHAT are the correct versions released. Are > these 7.0.103, 8.5.53, and 9.0.33 as shown on tomcat.apache.org, OR is it > 7.0.104, 8.5.54 and 9.0.34 as shown on ci.apache.org? > The first. CI

Version Question

Good afternoon Mark and group. There is a question as to WHAT are the correct versions released. Are these 7.0.103, 8.5.53, and 9.0.33 as shown on tomcat.apache.org, OR is it 7.0.104, 8.5.54 and 9.0.34 as shown on ci.apache.org? Thank you, Dream * Excel * Explore * Inspire Jon McAlexander

Re: Security audit raises questions (Tomcat 7.0.93)

On 3/18/20 4:03 AM, Mark Thomas replied to my questions: But I'm not sure (1) how security constraints interact with other security constraints, and See section 13.8.1 of the Servlet 4.0 spec. (2) whether they can go in the conf/web.xml as well as individual webapps' web.xml files. Yes

Re: How to pass the --enable-preview parameter when using JSVC?

Yes, I did try -X--enable-preview, was passed via jsvc, but not in a meaningful or understandable way to java/tomcat. On Thu, Mar 19, 2020 at 3:11 PM Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Ken, > > On 3/18/20 16:25,

Re: AW: AW: AJP Connector issue

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 RK, On 3/20/20 13:33, RK Ashburn wrote: > thanks Chirs. fixed it to an real ip, In many cases, 0.0.0.0 is basically the same as binding to the interface which represents the outside world (e.g. eth0, etc.). See my other reply in this thread to

Re: AW: AW: AJP Connector issue

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jon, On 3/20/20 13:28, jonmcalexan...@wellsfargo.com.INVALID wrote: > Christopher, > > Is there an entry that can go in the AJP connector to restrict > what addresses it will listen to requests from? Meaning you can list the IP addresses of the web

Re: AW: AW: AJP Connector issue

thanks Chirs. fixed it to an real ip, On Fri, Mar 20, 2020 at 12:40 PM Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > RK, > > On 3/20/20 09:57, RK Ashburn wrote: > > I have tested r successful AJP connector with apache proxy

RE: AW: AW: AJP Connector issue

Christopher, Is there an entry that can go in the AJP connector to restrict what addresses it will listen to requests from? Meaning you can list the IP addresses of the web servers? I know I'm top replying, but Outlook sucks with this. :-( Thanks, Dream * Excel * Explore * Inspire Jon

Re: AW: AW: AJP Connector issue

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 RK, On 3/20/20 09:57, RK Ashburn wrote: > I have tested r successful AJP connector with apache proxy on > (tomcat 7) > > 1. For AJP connector adding secretRequired="false" and address="0.0.0.0" > resolved my connectivity issue. I suspect the issue

Re: AW: AW: AW: AJP Connector issue

Hi Florian. The log below shows clearly "The AJP Connector is configured with secretRequired="true"". This probably comes from the fact that in your AJP Connector configuration, you either - have an explicit secretRequired="true" attribute or - you do not mention this attribute, and it

Re: AW: AW: AJP Connector issue

I have tested r successful AJP connector with apache proxy on (tomcat 7) 1. For AJP connector adding secretRequired="false" and address="0.0.0.0" resolved my connectivity issue. I suspect the issue you are having (with 403) is more like a permissions issue on the site the request is trying to

AW: OpenId with apache and tomcat

Hi Stephane, > -Ursprüngliche Nachricht- > Von: Stephane Passignat > Gesendet: 13 March 2020 17:53 > An: Tomcat Users List > Actually I have Apache2 operating as proxy and authenticate layer (HTTP > Form and HTTP Basic), in front of several Tomcat instances and webapps. > Apache

AW: AW: AW: AJP Connector issue

Just to make it clear what from my opinion the problem is: SCHWERWIEGEND [main] org.apache.catalina.core.StandardService.startInternal Failed to start connector [Connector[AJP/1.3-8011]] org.apache.catalina.LifecycleException: Der Start des Protokoll-Handlers ist fehlgeschlagen

Re: AW: AW: AJP Connector issue

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

AW: AW: AJP Connector issue

Here is the additional information: The error page looks like Tomcat: HTTP Status 403 – Forbidden _ Type Status Report Beschreibung Der Server hat die Anfrage verstanden, verbietet aber eine Autorisierung. _ Apache Tomcat/8.5.53 The Apache HTTPD log file says: - ""

[ANN] Apache Tomcat 7.0.103 released

The Apache Tomcat team announces the immediate availability of Apache Tomcat 7.0.103. Apache Tomcat is an open source software implementation of the Java Servlet, JavaServer Pages, Java Expression Language and Java WebSocket technologies. This release contains a number of bug fixes and

Re: AW: AJP Connector issue

On 20.03.2020 08:23, Fritze, Florian wrote: Hello Chris, thanks for the reply. Maybe I am doing something wrong, but setting secretRequired="false" does not solve my issue. Let me show you what I did and experience: I added to the Tomcat configuration and the ajp connector on the Apache HTTPD

AW: AJP Connector issue

Hello Chris, thanks for the reply. Maybe I am doing something wrong, but setting secretRequired="false" does not solve my issue. Let me show you what I did and experience: I added to the Tomcat configuration and the ajp connector on the Apache HTTPD side connects to 8011. When I now visit my