[tomcat] 01/02: Clean-up. Javadoc warnings with newer JDKs. Align with 8.5.x.

This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch 7.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git commit 8a648371516fda0d0034072c2833cd329201ea69 Author: Mark Thomas AuthorDate: Tue Jan 21 23:04:56 2020 + Clean-up. Jav

[tomcat] branch 7.0.x updated (1083b2e -> 2bf299a)

This is an automated email from the ASF dual-hosted git repository. markt pushed a change to branch 7.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git. from 1083b2e Clean-up. Align with 8.5.x/9.0.x/master new 8a64837 Clean-up. Javadoc warnings with newer JDKs. Align wi

[tomcat] 02/02: Improve logging of invalid HTTP header lines

This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch 7.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git commit 2bf299a366d206d0b0838ab99a79c206ef01f5eb Author: Mark Thomas AuthorDate: Tue Jan 21 22:24:37 2020 + Improve loggi

Re: Webinar on Tomcat 10 and Jakarta EE 9

На вт, 21.01.2020 г. в 19:28 Mark Thomas написа: > > All, > > There has been a fair amount of progress since ApacheCon EU. > > - We have a release plan for Tomcat 10 > - There is a schedule for Jakarta EE 9 > - Tomcat 10 has implemented the migrated APIs > - Eclipse has produced milestone releases

[tomcat] branch master updated: Add new connector attribute to control facade recycling

This is an automated email from the ASF dual-hosted git repository. remm pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/master by this push: new c7457dc Add new connector attribute to control fa

Re: [tomcat] branch master updated: Add new connector attribute to control facade recycling

On Wed, Jan 22, 2020 at 3:35 PM wrote: > This is an automated email from the ASF dual-hosted git repository. > > remm pushed a commit to branch master > in repository https://gitbox.apache.org/repos/asf/tomcat.git > > > The following commit(s) were added to refs/heads/master by this push: >

Re: [tomcat] branch master updated: Add new connector attribute to control facade recycling

On 22/01/2020 15:12, Rémy Maucherat wrote: > On Wed, Jan 22, 2020 at 3:35 PM > wrote: > > This is an automated email from the ASF dual-hosted git repository. > > remm pushed a commit to branch master > in repository https://gitbox.apache.org/repos/asf/tomcat.g

[Bug 64089] Resource paths resolve symlinks

https://bz.apache.org/bugzilla/show_bug.cgi?id=64089 --- Comment #1 from Mark Thomas --- I'm afraid I am going to take a different view. The behaviour you were relying on was a bug and, now that bug has been fixed, the behaviour has changed. For reference the change was as a result of this thre

[Bug 64082] Nio2Endpoint for async request doesn't clear OutputBuffer when socket has already been closed (response mixup)

https://bz.apache.org/bugzilla/show_bug.cgi?id=64082 --- Comment #4 from william.crow...@roguewave.com --- Setting org.apache.catalina.connector.RECYCLE_FACADES to true did work. Do you know why that fixed the issue? I am also concerned about the performance impact of setting that flag to true.

[Bug 64082] Nio2Endpoint for async request doesn't clear OutputBuffer when socket has already been closed (response mixup)

https://bz.apache.org/bugzilla/show_bug.cgi?id=64082 --- Comment #5 from Remy Maucherat --- I described the scenario in my comment, the application code is most likely not aware that the async is done. To know where the problem comes from a simple test case would be useful. -- You are receiving

[Bug 64082] Nio2Endpoint for async request doesn't clear OutputBuffer when socket has already been closed (response mixup)

https://bz.apache.org/bugzilla/show_bug.cgi?id=64082 --- Comment #6 from william.crow...@roguewave.com --- For a simple test case are you looking for application code? -- You are receiving this mail because: You are the assignee for the bug. --

[Bug 64089] Resource paths resolve symlinks

https://bz.apache.org/bugzilla/show_bug.cgi?id=64089 --- Comment #2 from Marvin Fröhlich --- Hi Mark, thanks a lot for taking a look at this. What a pity, that this is considered correct behavior. Couldn't this be configurable like allowLinking? I mean, it may be correct for many, but not for a

[Bug 64089] Resource paths resolve symlinks

https://bz.apache.org/bugzilla/show_bug.cgi?id=64089 --- Comment #3 from Marvin Fröhlich --- How about the difference between Linux and Windows? Shouldn't this fail on Windows, too, if it does on Linux? Or vice versa, work on both? -- You are receiving this mail because: You are the assignee fo