[Bug 53952] Add support for TLS 1.1 and 1.2

https://issues.apache.org/bugzilla/show_bug.cgi?id=53952 --- Comment #17 from Marcel Šebek sebe...@post.cz --- The problem is following. OpenSSL 0.9.8y defines SSL_OP_PKCS1_CHECK_{1,2} as 0x0800L and 0x1000L while OpenSSL 1.0.1e uses the same values for SSL_OP_NO_TLSv1_{1,2}, and defines

[Bug 53952] Add support for TLS 1.1 and 1.2

https://issues.apache.org/bugzilla/show_bug.cgi?id=53952 --- Comment #18 from Marcel Šebek sebe...@post.cz --- Created attachment 30149 -- https://issues.apache.org/bugzilla/attachment.cgi?id=30149action=edit patch dropping SSL_OP_PKCS* from supported_ssl_opts -- You are receiving this mail

[Bug 53952] Add support for TLS 1.1 and 1.2

https://issues.apache.org/bugzilla/show_bug.cgi?id=53952 Marcel Šebek sebe...@post.cz changed: What|Removed |Added Attachment #30111|0 |1 is

[Bug 54800] New: Possible thread/memory leak with use of WebSocketContainer

https://issues.apache.org/bugzilla/show_bug.cgi?id=54800 Bug ID: 54800 Summary: Possible thread/memory leak with use of WebSocketContainer Product: Tomcat 8 Version: trunk Hardware: PC OS: Linux

[Bug 54801] New: EL-like expressions in jsp:scriptlet break compilation of tag files using XML syntax

https://issues.apache.org/bugzilla/show_bug.cgi?id=54801 Bug ID: 54801 Summary: EL-like expressions in jsp:scriptlet break compilation of tag files using XML syntax Product: Tomcat 7 Version: 7.0.39 Hardware: PC

[Bug 54801] EL-like expressions in jsp:scriptlet break compilation of tag files using XML syntax

https://issues.apache.org/bugzilla/show_bug.cgi?id=54801 --- Comment #1 from Konstantin Kolinko knst.koli...@gmail.com --- Created attachment 30153 -- https://issues.apache.org/bugzilla/attachment.cgi?id=30153action=edit Stacktrace (current 7.0 = 7.0.39) -- You are receiving this mail

[Bug 54802] New: Provide location information for exceptions thrown by JspDocumentParser

https://issues.apache.org/bugzilla/show_bug.cgi?id=54802 Bug ID: 54802 Summary: Provide location information for exceptions thrown by JspDocumentParser Product: Tomcat 7 Version: 7.0.39 Hardware: PC OS:

[Bug 54802] Provide location information for exceptions thrown by JspDocumentParser

https://issues.apache.org/bugzilla/show_bug.cgi?id=54802 --- Comment #1 from Konstantin Kolinko knst.koli...@gmail.com --- Created attachment 30154 -- https://issues.apache.org/bugzilla/attachment.cgi?id=30154action=edit Text of Error page shown for bug 54801 by current trunk Text of error

svn commit: r1464781 - /tomcat/trunk/java/org/apache/jasper/compiler/JspDocumentParser.java

Author: kkolinko Date: Thu Apr 4 23:00:53 2013 New Revision: 1464781 URL: http://svn.apache.org/r1464781 Log: Fix https://issues.apache.org/bugzilla/show_bug.cgi?id=54802 Provide location information for exceptions thrown by JspDocumentParser Modified:

[Bug 54802] Provide location information for exceptions thrown by JspDocumentParser

https://issues.apache.org/bugzilla/show_bug.cgi?id=54802 --- Comment #2 from Konstantin Kolinko knst.koli...@gmail.com --- Created attachment 30155 -- https://issues.apache.org/bugzilla/attachment.cgi?id=30155action=edit Text of Error page shown for bug 54801 by trunk with r1464781 Fixed in

buildbot success in ASF Buildbot on tomcat-trunk

The Buildbot has detected a restored build on builder tomcat-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/tomcat-trunk/builds/4200 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: bb-vm_ubuntu Build Reason: scheduler Build

DefaultServlet HttpServletResponse.setContentType called after HttpServletResponse.getOutputStream

In the DefaultServlet the content type is determined before the call to getOutputStream and then header is set after the call to getOutputStream, how logical is this? I think it should set the content type header before the first call to getOutputStream so that the content type is exposed to