RE: how to prevent user access to JSP pages?

If it helps, I also needed to do something very similar where if the user connected to the right server running Tomcat and has the right port but wrong context or servlet, they would see a default Tomcat page not found revealing the application server used (Tomcat) and its version which for us

RE: AT WITS END regarding JVM arguments

-Original Message- From: James H. H. Lampert [mailto:jam...@touchtonecorp.com] Sent: Tuesday, September 06, 2016 6:59 PM To: Tomcat Users List Subject: Re: AT WITS END regarding JVM arguments On 9/6/16, 8:05 AM, Christopher Schultz wrote: > It's worth noting

RE: Configuring certificate for ssl support on Tomcat 8.5

-Original Message- From: Mark Thomas [mailto:ma...@apache.org] Sent: Wednesday, August 31, 2016 10:52 AM To: Tomcat Users List Subject: Re: Configuring certificate for ssl support on Tomcat 8.5 On 31/08/2016 15:45, Lazar Kirchev wrote: > Hello, > > According to

RE: Tomcat 8.x JvmOptions parameter length restrictions?

List <users@tomcat.apache.org> Subject: Re: Tomcat 8.x JvmOptions parameter length restrictions? On 8/29/2016 8:34 AM, Mekkelsen Madden, Steve wrote: > I've setup Tomcat 8.5.3 as a Windows Service (configured the service.bat > file) and everything appears to be working fine. I'm trying

Tomcat 8.x JvmOptions parameter length restrictions?

I've setup Tomcat 8.5.3 as a Windows Service (configured the service.bat file) and everything appears to be working fine. I'm trying to find out if there are any restrictions to the overall length of the parameters which can be used in the service.bat for --JvmOptions " " ^ line. This isn't

RE: Tomcat starts but home page cannot open with url http://localhost:8080

sekhar [mailto:chandra.c...@gmail.com] Sent: Thursday, July 21, 2016 11:29 PM To: Mekkelsen Madden, Steve <steve.mekkelsenmad...@pega.com> Cc: Tomcat Users List <users@tomcat.apache.org> Subject: Re: Tomcat starts but home page cannot open with url http://localhost:8080 Actually, i didn

RE: Tomcat starts but home page cannot open with url http://localhost:8080

To: Mekkelsen Madden, Steve <steve.mekkelsenmad...@pega.com> Cc: Tomcat Users List <users@tomcat.apache.org> Subject: Re: Tomcat starts but home page cannot open with url http://localhost:8080 Hi Steve, Please find the below details. 1.The port 8080 is available.But,need to check if there i

RE: Tomcat starts but home page cannot open with url http://localhost:8080

Still not enough detail to help. Did you look at the log files to see what errors are occurring during Tomcat startup? Assuming no firewall is blocking port 8080 on the machine you untarred it too, if you did take a full backup by tar'ing the entire folder with the webapps folder too, it

RE: SSL/TLS 8.5.3 upgrade from 8.0.32 using NIO2 url encoding issues

-Original Message- From: Felix Schumacher [mailto:felix.schumac...@internetallee.de] Sent: Thursday, July 07, 2016 12:53 PM To: users@tomcat.apache.org Subject: Re: SSL/TLS 8.5.3 upgrade from 8.0.32 using NIO2 url encoding issues Am 07.07.2016 um 18:32 schrieb Mekkelsen Madden, Steve: > Ev

RE: SSL/TLS 8.5.3 upgrade from 8.0.32 using NIO2 url encoding issues

schrieb Mekkelsen Madden, Steve: > Hi, sorry for delay and misinformation of the screenshot. The screenshot > shows Fiddler seeing the correct xml using both NIO and NIO2 protocols. > Fiddler does not see anything wrong with the requests themselves. However, > when we enable mo

RE: SSL/TLS 8.5.3 upgrade from 8.0.32 using NIO2 url encoding issues

[mailto:ch...@christopherschultz.net] Sent: Wednesday, July 06, 2016 4:45 PM To: Tomcat Users List <users@tomcat.apache.org> Subject: Re: SSL/TLS 8.5.3 upgrade from 8.0.32 using NIO2 url encoding issues -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Steve, On 7/6/16 4:22 PM, Mekkelsen

RE: SSL/TLS 8.5.3 upgrade from 8.0.32 using NIO2 url encoding issues

...@pega.com | www.pega.com -Original Message- From: Mekkelsen Madden, Steve Sent: Wednesday, July 06, 2016 3:44 PM To: users@tomcat.apache.org Subject: RE: SSL/TLS 8.5.3 upgrade from 8.0.32 using NIO2 url encoding issues Thanks Felix. See below -Original Message- From: Felix

RE: SSL/TLS 8.5.3 upgrade from 8.0.32 using NIO2 url encoding issues

Mekkelsen Madden, Steve: > This particular issue has raised a lot of issues in-house and we would > greatly appreciate a response from someone having more details on why NIO2 no > longer works. > > Thanks! > > > -Original Message- > From: Mekkelsen Madden, St

RE: SSL/TLS 8.5.3 upgrade from 8.0.32 using NIO2 url encoding issues

This particular issue has raised a lot of issues in-house and we would greatly appreciate a response from someone having more details on why NIO2 no longer works. Thanks! -Original Message- From: Mekkelsen Madden, Steve Sent: Friday, July 01, 2016 12:56 PM To: Tomcat Users List

SSL/TLS 8.5.3 upgrade from 8.0.32 using NIO2 url encoding issues

Hi all, Is anyone aware of why after upgrading from Tomcat 8.0.32x64 (Windows) to 8.5.3x64 using the connector protocol of: protocol="org.apache.coyote.http11.Http11Nio2Protocol" fails with url encoding errors? Once it was changed back to

RE: Need help with URL redirecting

One thing you could do is have an entry in your webapps\ROOT folder called like: MyAppRedirect.html (name can be anything) Inside the file you need something like: In your conf\web.xml at the bottom of it, you'll see 3 lines shown below: index.html index.htm