Re: WebSocket Handshake returns Unexpected Response Code 500

OK, apparently HandshakeRequest's getRequestURI().getAuthority() returns null and my code didn't account for that. I'm surprised that nothing was logged anywhere though, even with a FINE log level. Igal Sapir Lucee Core Developer Lucee.org On 12/6/2016 5:18 PM, Igal @ Lu

Re: WebSocket Handshake returns Unexpected Response Code 500

On 12/6/2016 4:25 PM, Igal @ Lucee.org wrote: This is a cross post with http://stackoverflow.com/questions/41007216/websocket-handshake-on-tomcat-returns-unexpected-response-code-500 : I have a WebSocket application that registers the endpoint programmatically, without the use of Annotation

WebSocket Handshake returns Unexpected Response Code 500

This is a cross post with http://stackoverflow.com/questions/41007216/websocket-handshake-on-tomcat-returns-unexpected-response-code-500 : I have a WebSocket application that registers the endpoint programmatically, without the use of Annotations. The relevant code is: |ServerEndpointConfig

Re: Connector bindOnInit=false not behaving as expected

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 12/6/16 4:17 AM, Mark Thomas wrote: > On 05/12/2016 23:03, Christopher Schultz wrote: >> Mark, >> >> On 12/4/16 3:24 PM, Mark Thomas wrote: >> It looks like the ProtocolHandler is really the place >> where the TLS configuration is

Re: Connector bindOnInit=false not behaving as expected

On 05/12/2016 23:03, Christopher Schultz wrote: > Mark, > > On 12/4/16 3:24 PM, Mark Thomas wrote: > It looks like the ProtocolHandler is really the place where > the TLS configuration is taking effect, and not the > Connector, so I'm largely ignoring the Connector for now. Is > th

Re: SSDLC Compliance

On 06/12/2016 07:21, GAN Kok Leong, Adrian wrote: > Hi, > > We have a cybersecurity requirement for all software. We would like > to know whether Tomcat version 7.0.25 is developed and comply with > Secure Software Development Life Cycle (SSDLC)? This sounds suspiciously like a security box ticki