https://bz.apache.org/bugzilla/show_bug.cgi?id=59703
--- Comment #2 from Huxing Zhang ---
We ran into the same issue in 8.5.x, as a result, we've chosen to use
org.apache.tomcat.util.http.LegacyCookieProcessor instead for compatibility.
As there is another one commenting on this issue (see bott
The proposed 8.5.14 release is:
[ ] Broken - do not release
[ X ] Stable - go ahead and release as 8.5.14
Test case: ok
Our test web application works fine
--
From:Mark Thomas
Time:2017 Apr 13 (Thu) 21:13
To:Tomcat Developers List
https://bz.apache.org/bugzilla/show_bug.cgi?id=60963
--- Comment #6 from Thomas Meyer ---
Regarding ZipInputStreamWithPosition:
I think you found the ugly part of this patch. I guess your suggestion wouldn't
work, because ZipInputStream will construct itself with a new
PushBackInputstream and the
https://bz.apache.org/bugzilla/show_bug.cgi?id=60963
--- Comment #5 from Thomas Meyer ---
Regarding file locking issue: I didn't check this. I'll try to test this.
--
You are receiving this mail because:
You are the assignee for the bug.
-
On Wed, Apr 12, 2017 at 10:11 PM, Mark Thomas wrote:
> The proposed Apache Tomcat 9.0.0.M20 release is now available for voting.
>
> This is a milestone release for the 9.0.x branch. It should be
> noted that, as a milestone release:
> - Servlet 4.0 is not finalised
> - The EGs have not started w
On Thu, Apr 13, 2017 at 3:12 PM, Mark Thomas wrote:
> The proposed Apache Tomcat 8.5.14 release is now available for voting.
>
> The major changes compared to the 8.5.13 release are:
>
> - Correct a regression that broke JMX operations (including the Manager
> web application) if the operation
Hi,
The proposed 9.0.0.M20 release is:
[ ] Broken - do not release
[ X ] Alpha - go ahead and release as 9.0.0.M20
Test cases: ok.
Our test web app works fine.
--
From:Mark Thomas
Time:2017 Apr 13 (Thu) 04:20
To:Tomcat Developers L
https://bz.apache.org/bugzilla/show_bug.cgi?id=60769
--- Comment #8 from Lazar ---
Created attachment 34914
--> https://bz.apache.org/bugzilla/attachment.cgi?id=34914&action=edit
Correct war for reproducing the exotic encoding problem
--
You are receiving this mail because:
You are the assign
https://bz.apache.org/bugzilla/show_bug.cgi?id=60769
Lazar changed:
What|Removed |Added
Attachment #34913|0 |1
is obsolete|
Author: kfujino
Date: Fri Apr 14 08:17:17 2017
New Revision: 1791325
URL: http://svn.apache.org/viewvc?rev=1791325&view=rev
Log:
Add features to get the statistics of the thread pool of the Receiver component.
These statistics information can be acquired via JMX.
Modified:
tomcat/trunk/java/o
https://bz.apache.org/bugzilla/show_bug.cgi?id=60769
--- Comment #6 from Lazar ---
Created attachment 34913
--> https://bz.apache.org/bugzilla/attachment.cgi?id=34913&action=edit
Sample war with jspx in exotic encoding
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60769
--- Comment #5 from Lazar ---
The content of the enctest.jspx is:
http://java.sun.com/JSP/Page";>
You should see this text.
So actually there is an encoding attribute in the prolog. For some reason JRE
XML parser does not detect i
On 14/04/2017 07:43, Keiichi Fujino wrote:
> 2017-04-13 22:12 GMT+09:00 Mark Thomas :
>
>> The proposed Apache Tomcat 8.5.14 release is now available for voting.
>>
>> The major changes compared to the 8.5.13 release are:
>>
>> - Correct a regression that broke JMX operations (including the Manage
13 matches
Mail list logo
