https://bz.apache.org/bugzilla/show_bug.cgi?id=61932
--- Comment #3 from Daniel Qian ---
(In reply to Mark Thomas from comment #1)
> I'm planning on taking a look at this today. Does the client need to do
> anything to trigger this or is a simple POST sufficient? I'll try the simple
> POST but if
The Buildbot has detected a restored build on builder tomcat-8-trunk while
building . Full details are available at:
https://ci.apache.org/builders/tomcat-8-trunk/builds/1206
Buildbot URL: https://ci.apache.org/
Buildslave for this Build: silvanus_ubuntu
Build Reason: The AnyBranchScheduler
https://bz.apache.org/bugzilla/show_bug.cgi?id=61932
Mark Thomas changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
Author: markt
Date: Wed Jan 3 20:52:18 2018
New Revision: 1820011
URL: http://svn.apache.org/viewvc?rev=1820011&view=rev
Log:
Fix https://bz.apache.org/bugzilla/show_bug.cgi?id=61932
Allow a call to AsyncContext.dispatch() to terminate non-blocking I/O.
Modified:
tomcat/tc8.0.x/trunk/ (pro
The Buildbot has detected a restored build on builder tomcat-trunk while
building . Full details are available at:
https://ci.apache.org/builders/tomcat-trunk/builds/2929
Buildbot URL: https://ci.apache.org/
Buildslave for this Build: silvanus_ubuntu
Build Reason: The AnyBranchScheduler sch
Author: markt
Date: Wed Jan 3 20:15:46 2018
New Revision: 1820007
URL: http://svn.apache.org/viewvc?rev=1820007&view=rev
Log:
Fix https://bz.apache.org/bugzilla/show_bug.cgi?id=61932
Allow a call to AsyncContext.dispatch() to terminate non-blocking I/O.
Modified:
tomcat/tc8.5.x/trunk/ (pro
Author: markt
Date: Wed Jan 3 20:11:52 2018
New Revision: 1820005
URL: http://svn.apache.org/viewvc?rev=1820005&view=rev
Log:
Fix typo
Modified:
tomcat/trunk/test/org/apache/catalina/nonblocking/TestNonBlockingAPI.java
Modified:
tomcat/trunk/test/org/apache/catalina/nonblocking/TestNonBloc
Author: markt
Date: Wed Jan 3 20:03:15 2018
New Revision: 1820003
URL: http://svn.apache.org/viewvc?rev=1820003&view=rev
Log:
Fix https://bz.apache.org/bugzilla/show_bug.cgi?id=61932
Allow a call to AsyncContext.dispatch() to terminate non-blocking I/O.
Modified:
tomcat/trunk/java/org/apache
Github user kdombeck commented on the issue:
https://github.com/apache/tomcat/pull/96
@markt-asf I haven't received any responses to the
[thread](http://tomcat.10.x6.nabble.com/Change-HTTP-status-code-for-DefaultServlet-with-readOnly-set-to-true-td5070373.html)
I started on dev@. I kn
Github user ChristopherSchultz commented on the issue:
https://github.com/apache/tomcat/pull/96
I think 405 is more appropriate when the method is in fact not allowed
(readOnly). As for POST, there is nothing "writey" about POST, whereas PUT and
DELETE have definite "write" semantics.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61932
--- Comment #1 from Mark Thomas ---
I'm planning on taking a look at this today. Does the client need to do
anything to trigger this or is a simple POST sufficient? I'll try the simple
POST but if there is more to it it would be helpful to know
https://bz.apache.org/bugzilla/show_bug.cgi?id=61948
--- Comment #7 from Mark Thomas ---
FYI I went through the SNI parsing code manually and as far as I could tell the
two provided test cases covered the two possible exception types for malformed
input. There was the possibility of an IndexOutOf
https://bz.apache.org/bugzilla/show_bug.cgi?id=61948
--- Comment #6 from Remy Maucherat ---
This is the way I was planning to do it, so good.
Evgenij, please let us know if you find any legitimate TLS records that would
cause an exception (the debug level will now hide the fact the connection is
13 matches
Mail list logo
