Tomcat web socket not sending more than one message to the client

Hello, I have a problem with Tomcat only sending the first message to the client and then no message anymore till the client reconnects. The code was working for some versions but then stopped working: public void handleEvent(EventObject eventObject) { Enumeration

Re: Consecutive double slashes in URLs

On 18/10/17 22:23, Maor Shiffman wrote: > On Wed, Oct 18, 2017 at 11:58 PM, Mark Thomas wrote: > >> On 18/10/17 21:49, Maor Shiffman wrote: >> >>> Hi, >>> >>> ​Attached are two war files that demonstrate the issue - ROOT.war and >>> context2.war. >>> There are two contexts -

Re: TLS support: consider bundling native libs in JARs

Hi Mark, Christopher, On Thu, Oct 19, 2017 at 7:32 PM, Christopher Schultz wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Mark, > > On 10/19/17 1:22 PM, Mark Thomas wrote: > > On 19/10/17 16:56, Mark Thomas wrote: > >> On 19 October 2017 15:11:19

TLS support: consider bundling native libs in JARs

Hi, More and more servers are choosing to make available one or more solutions to use TLS native stacks by shipping them as JARs: * Netty has quite a few options there http://netty.io/wiki/forked-tomcat-native.html * Jetty is now shipping a conscrypt support as well

The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.

Dear expert, Today I receive an error message that I have never come across. "Https status 404 - not found " "The origin server did not find a current representation for the target resource or is not willing to disclose that one exists." I have googled but there is no solution that can help

Re: Tomcat web socket not sending more than one message to the client

Hello, after waiting 35 minutes suddenly some events get forwarded for a second or two and then again silence. This is really strange. Kind Regards, Christoph Mit freundlichen Grüßen Christoph Mertins On Thu, Oct 19, 2017 at 10:21 AM, Christoph Mertins wrote: > Hello, >

Re: Fwd: Content-Type is turned to lower when passed through mod_jk - this looks to be a bug.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 10/15/17 6:54 PM, Mark O'Donohue wrote: > Hi > > Just wanted an opinion on this before I logged a bug report against > mod_jk.c > > > Running our proxied request via mod_jk we are seeing the returned > content-type being changing to all

Re: More, Re: Weird problem: browsers refusing to connect; more "fun with ciphers clauses on the connector tag"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 James, On 10/16/17 2:35 PM, James H. H. Lampert wrote: > I just got finished going through 20 other customer Tomcat > installations we administer. > > First, I found that most of them were accepting the DHE ciphers > I'd disabled on the problem

Re: Need suggestion in upgrading Apache Tomcat due to security vulnerability in Apache Tomcat 7.0.61

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Naga, On 10/17/17 2:49 AM, naga karthikeyan wrote: > Recently we found there is security vulnerability in Apache Tomcat > 7.0.61. Please note that now our application runs on Apache Tomcat > 7.0.61. > > Please advice me whether I can upgrade

Re: TLS support: consider bundling native libs in JARs

On 19 October 2017 15:11:19 BST, Brian Clozel wrote: >Hi, > >More and more servers are choosing to make available one or more >solutions >to use TLS native stacks by shipping them as JARs: > >* Netty has quite a few options there >http://netty.io/wiki/forked-tomcat-native.html

Re: TLS support: consider bundling native libs in JARs

On 19/10/17 16:56, Mark Thomas wrote: > On 19 October 2017 15:11:19 BST, Brian Clozel wrote: >> Hi, >> >> More and more servers are choosing to make available one or more >> solutions >> to use TLS native stacks by shipping them as JARs: >> >> * Netty has quite a few options

Re: TLS support: consider bundling native libs in JARs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 10/19/17 1:22 PM, Mark Thomas wrote: > On 19/10/17 16:56, Mark Thomas wrote: >> On 19 October 2017 15:11:19 BST, Brian Clozel >> wrote: >>> Hi, >>> >>> More and more servers are choosing to make available one or >>>

Re: More, Re: Weird problem: browsers refusing to connect; more "fun with ciphers clauses on the connector tag"

On 10/19/17, 10:02 AM, Christopher Schultz wrote: The browser tells the server what cipher suites it supports during the initial handshake, and the server decides which algorithm to use. The client doesn't try multiple different connections to see which one sticks. The server either replies

Re: Response change between 8.5.x and 8.0.x (and earlier versions) W.R.T. Line separator CRLF vs. LF

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Adam, On 10/17/17 12:12 PM, Adam Rauch wrote: > On 10/16/2017 1:27 PM, Net Dawg wrote: >> Profuse apologies. We are unable reproduce this. However out >> tests were failing for another reason. 8.5.23 returns 400 error >> with header "HTTP/1.1