https://bz.apache.org/bugzilla/show_bug.cgi?id=61751
--- Comment #19 from Markus Dörschmidt ---
Thank you very much. The bug is fixed!
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe,
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751
Mark Thomas changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751
Mark Thomas changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751
--- Comment #16 from Remy Maucherat ---
I added a follow up: http://svn.apache.org/viewvc?rev=1824201&view=rev
As this didn't happen with the regular JSSE engine, I think the missing
underflow status is the root cause (the unwrap loops in Secu
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751
--- Comment #15 from Remy Maucherat ---
On second thought, this will need to be revisited as the blocking read of
SecureNio2Channel is supposed to block until it returns non 0. Of course, the
algorithm is complex already ...
I will add a TODO c
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751
--- Comment #14 from Remy Maucherat ---
Great job on that fix ! :)
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-uns
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751
Mark Thomas changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751
--- Comment #12 from Mark Thomas ---
I've found the root cause. A blocking read obtained bytes from the network but
after unwrapping there were zero application bytes. Since this is a blocking
read, more network bytes should be read and unwrapp
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751
--- Comment #11 from Mark Thomas ---
Thanks for the additional information. I can now reproduce this (thanks to
Microsoft for the free azure credits).
I have two clean Tomcat 9.0.x builds. One locally, one on Azure. Key config is
HTTPS / OpenS
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751
Markus Dörschmidt changed:
What|Removed |Added
Resolution|WORKSFORME |---
Version|8.5.16
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751
Remy Maucherat changed:
What|Removed |Added
Status|NEEDINFO|RESOLVED
Resolution|---
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751
--- Comment #8 from Mark Thomas ---
I can't reproduce this problem with the given test case either. I've tested:
- NIO2
- 8.5.x trunk
- http and https
- https with OpenSSL (Tomcat native 1.2.16, OpenSSL ubuntu latest)
- https with JSSE
- Java 1
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751
--- Comment #7 from Remy Maucherat ---
As I said, I tried the same connector with your test upload, it worked for me.
This issue is not very well presented IMO, for instance it seems to imply it is
a NIO2 + OpenSSL issue only, but in the end t
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751
--- Comment #6 from Markus Dörschmidt ---
The real web application uses Spring Webservices 2.4.0.
The SOAP request contains a base64-encoded binary element.
The SOAP request never reaches the Webservice framework, because parsing the
XML docu
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751
--- Comment #5 from Remy Maucherat ---
This works for me.
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751
--- Comment #4 from Markus Dörschmidt ---
I attached a simple web application to reproduce the code.
Try sending XML data to application using curl:
curl -X POST -k --header "Content-Type: text/xml;charset=UTF-8" --data
@"test.xml"
After ca
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751
--- Comment #3 from Markus Dörschmidt ---
Created attachment 35539
--> https://bz.apache.org/bugzilla/attachment.cgi?id=35539&action=edit
Minimal code to reproduce bug
--
You are receiving this mail because:
You are the assignee for the bug
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751
Mark Thomas changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #2 from Mark Thomas
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751
--- Comment #1 from Remy Maucherat ---
Do you think you could give some pointers on reproduction ?
In the past there was BZ57799 which was caused by an unexpected interaction
with use of available() by the framework.
--
You are receiving this
19 matches
Mail list logo