DO NOT REPLY [Bug 51698] New: ajp CPing/Forward-Request packet forgery, is a design decision? or a security vulnerability?

https://issues.apache.org/bugzilla/show_bug.cgi?id=51698 Bug #: 51698 Summary: ajp CPing/Forward-Request packet forgery, is a design decision? or a security vulnerability? Product: Tomcat 7 Version: 7.0.20 Platform: PC

DO NOT REPLY [Bug 51698] ajp CPing/Forward-Request packet forgery, is a design decision? or a security vulnerability?

https://issues.apache.org/bugzilla/show_bug.cgi?id=51698 --- Comment #1 from zhh 2011-08-20 07:55:51 UTC --- Created attachment 27417 --> https://issues.apache.org/bugzilla/attachment.cgi?id=27417 ajp Forward-Request packet forgery second example: ajp Forward-Request packet forgery -- Config

Re: Votes needed for 5.5.x

I should be back from vacation tomorrow evening so I can start the formal release process Monday! :) On Aug 16, 2011, at 6:38 AM, Mark Thomas wrote: > With Jim likely to be rolling a 5.5.x release next week I have been > looking at the 5.5.x status file. There are a handful of issues that > need

Re: svn commit: r1159673 - in /tomcat/tc7.0.x/trunk: java/org/apache/catalina/core/JreMemoryLeakPreventionListener.java webapps/docs/changelog.xml webapps/docs/config/listeners.xml

Konstantin, On 8/19/2011 3:11 PM, Konstantin Kolinko wrote: > Mark cleared the changelog file after creating the branch. > > The idea is that > * work is done on trunk > * it is merged to tc7.0.x > * items merged to tc7.0.x go into TC7's changelog file and those that > won't be merged go into TC