AW: https redirect failed for POST request when behind a load balancer

Bin, > Peter: > Here is what I got when using curl on a client. > curl -I http://lb-api:8080/urls?param1=something\=123 > HTTP/1.0 302 Found > Location: https://lb-api:8443/ urls?param1=something\=123 > Server: BigIP > Connection: Keep-Alive > Content-Length: 0 > So it is working as designed in

[ANN] Apache Tomcat 7.0.75 released

The Apache Tomcat team announces the immediate availability of Apache Tomcat 7.0.75. 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: Separate and Redirect Tomcat Embedded 8.5.6 Log

Hi Chris, Thanks for your answer. But this seems to not change anything. It's there a way to get an InputStream() for each context? Or set a logger or something? From what I saw I can only getLogger() but I cant add a FileHandler to this. Costin -Original Message- From: Christopher

[ANN] Apache Tomcat 8.0.41 available

The Apache Tomcat team announces the immediate availability of Apache Tomcat 8.0.41. Please note that Tomcat 8.x users should normally be using 8.5.x releases in preference to 8.0.x releases. Apache Tomcat 8.0 is an open source software implementation of the Java Servlet, JavaServer Pages, Java

RE: Mutual certificate authentication between Tomcat and MS IIS

Thanks, we will try your suggestions. In the meantime we logged a request in Microsoft. I'll keep you posted. -Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: 24 January 2017 22:46 To: Tomcat Users List Subject: Re: Mutual certificate

Re: embedded tomcat (8.0.39) shared jars

I've examined the issue more closely. The class (interface) is loaded twice, once by WebappClassLoader and once by Launcher$AppClassLoader, both from StandardContext.listenerStart() line: 4853 The WebappClassLoader one is reached via regular method calls, the other through reflection:

Re: Character encoding issue in URL

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Justin, On 1/25/17 12:25 AM, Justin Dang wrote: > Hi, I have a clean install of an older version of Tomcat (8.0.24). > I have noticed when a character is encoded in the URL, Tomcat fails > to return the URL requested. I've noted this same request

Re: How to configure tomcat to ignore large websocket messages

On 25/01/2017 21:12, Preston Price wrote: > So what is the purpose of a Decoder.TextStream then if not to handle > incomplete/partial messages? To interface with other components that wanted to process the data in that form. Partial messages feeding an InputStream is doable, but you need to

Re: Problems with tomcat 9 http/2 configuration

On 25/01/2017 22:11, Zigarelli, Michael wrote: > Hi, > > > I am unable to configure tomcat 9.0.0.M17 for http/2 support. My connector > for port 8443 has been uncommented and the necessary certificates were added > to it. I am receiving this error when I start my tomcat: Jan 25, 2017 4:28:21

RE: https redirect failed for POST request when behind a load balancer

Peter: Checked F5 and found that it was the proper behavior of F5 in this http to https redirect. There is a way to use iRule to change that. Thank you very much! Bin -Original Message- From: Kreuser, Peter [mailto:pkreu...@airplus.com] Sent: Wednesday, January 25, 2017 1:22 AM To:

Re: HTTP response reason phrases

2017-01-24 20:08 GMT+01:00 Christopher Schultz : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > All, > > I'm cross-posting dev@ and users@, but please only reply to dev@ if > you'd like to get involved in this discussion. > > I'd like to openly-discuss

Problems with tomcat 9 http/2 configuration

Hi, I am unable to configure tomcat 9.0.0.M17 for http/2 support. My connector for port 8443 has been uncommented and the necessary certificates were added to it. I am receiving this error when I start my tomcat: Jan 25, 2017 4:28:21 PM org.apache.catalina.util.LifecycleBase

Re: Apache/Tomcat vulnerability

hi, i just wanted to let you know that the we have migrated to WildFly application server and our server is up online 24/24h from three weeks. Since this time it has never freezed so I suppose i was right saying somebody found DoS exploit on tomcat. Unfortunately I cannot help you in figure

Re: How to configure tomcat to ignore large websocket messages

Is it possible to use a Decoder to handle partial websocket messages? On Wed, Jan 25, 2017 at 1:29 PM, Mark Thomas wrote: > On 25/01/2017 20:25, Preston Price wrote: > > My environment: > > java: 1.8.0_102, > > tomcat: 8.0.39, > > os:Ubuntu 4.4.0-45-generic, > > websocket api:

Re: How to configure tomcat to ignore large websocket messages

On 25/01/2017 20:53, Preston Price wrote: > Is it possible to use a Decoder to handle partial websocket messages? No. Decoders only apply to whole messages. The closest you will get it is: - remove the message size limit - use a partial message handler that buffers up to a limit - discard data

Re: How to configure tomcat to ignore large websocket messages

So what is the purpose of a Decoder.TextStream then if not to handle incomplete/partial messages? Cheers! On Wed, Jan 25, 2017 at 2:07 PM, Mark Thomas wrote: > On 25/01/2017 20:53, Preston Price wrote: > > Is it possible to use a Decoder to handle partial websocket messages?

How to configure tomcat to ignore large websocket messages

My environment: java: 1.8.0_102, tomcat: 8.0.39, os:Ubuntu 4.4.0-45-generic, websocket api: 1.1 Currently in my application clients will (rarely) send a message that exceeds the default (8192 byte) limit for messages. This results in the socket being closed by the server with a 1009 code (too

Re: How to configure tomcat to ignore large websocket messages

On 25/01/2017 20:25, Preston Price wrote: > My environment: > java: 1.8.0_102, > tomcat: 8.0.39, > os:Ubuntu 4.4.0-45-generic, > websocket api: 1.1 > > Currently in my application clients will (rarely) send a message that > exceeds the default (8192 byte) limit for messages. This results in the >