[tomcat] branch 7.0.x updated: Add release date for 7.0.108

This is an automated email from the ASF dual-hosted git repository. violetagg pushed a commit to branch 7.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/7.0.x by this push: new 46b3699 Add release date for 7.0.108 46b3699 i

svn commit: r45840 - /dev/tomcat/tomcat-7/v7.0.108/ /release/tomcat/tomcat-7/v7.0.108/

Author: violetagg Date: Fri Feb 5 06:50:43 2021 New Revision: 45840 Log: Release Tomcat 7.0.108 Added: release/tomcat/tomcat-7/v7.0.108/ - copied from r45839, dev/tomcat/tomcat-7/v7.0.108/ Removed: dev/tomcat/tomcat-7/v7.0.108/

Re: [RESULT][VOTE] Release Apache Tomcat 7.0.108

Hi, На чт, 28.01.2021 г. в 11:48 ч. Violeta Georgieva написа: > > The proposed Apache Tomcat 7.0.108 release is now available for voting. > > It can be obtained from: > https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.108/ > The Maven staging repo is: > https://repository.apache.org/co

Re: [VOTE] Release Apache Tomcat 7.0.108

Am 28.01.21 um 10:48 schrieb Violeta Georgieva: > The proposed Apache Tomcat 7.0.108 release is now available for voting. > > It can be obtained from: > https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.108/ > The Maven staging repo is: > https://repository.apache.org/content/repositori

Re: Applications setting connection specific HTTP headers

+1, out of curiosity, cant rewrite valve help somehow? Le jeu. 4 févr. 2021 à 19:11, Mark Thomas a écrit : > On 04/02/2021 17:56, Romain Manni-Bucau wrote: > > I always fixed it by a filter until now. > > What about adding a filter in tomcat and if users complain move to > another > > solution?

Re: Applications setting connection specific HTTP headers

On 04/02/2021 17:56, Romain Manni-Bucau wrote: > I always fixed it by a filter until now. > What about adding a filter in tomcat and if users complain move to another > solution? Can even be marked @Alpha for a few I guess. We have been talking about a ModHeadersFilter for quite some time. This m

Re: Applications setting connection specific HTTP headers

I always fixed it by a filter until now. What about adding a filter in tomcat and if users complain move to another solution? Can even be marked @Alpha for a few I guess. Romain Manni-Bucau @rmannibucau | Blog | Old Blog

Re: Applications setting connection specific HTTP headers

On 04/02/2021 16:37, Romain Manni-Bucau wrote: > (if it helps) From what I saw which was close to that it was due to the > current microservice erea where it is very common to have poor man proxies > coded in java/tomcat and forwarding all headers of a HTTP request, this is > not uncommon and will

Re: Applications setting connection specific HTTP headers

Am 2021-02-04 um 17:36 schrieb Rémy Maucherat: On Thu, Feb 4, 2021 at 5:31 PM Michael Osipov wrote: Am 2021-02-03 um 13:03 schrieb Mark Thomas: Hi all, We have an open PR related to this for HTTP/2 (#277) and I am seeing related issues at $work with HTTP. In short, applications are doing th

Re: Applications setting connection specific HTTP headers

(if it helps) From what I saw which was close to that it was due to the current microservice erea where it is very common to have poor man proxies coded in java/tomcat and forwarding all headers of a HTTP request, this is not uncommon and will even work on some containers (and always in bad tests ;

Re: Applications setting connection specific HTTP headers

On Thu, Feb 4, 2021 at 5:31 PM Michael Osipov wrote: > Am 2021-02-03 um 13:03 schrieb Mark Thomas: > > Hi all, > > > > We have an open PR related to this for HTTP/2 (#277) and I am seeing > > related issues at $work with HTTP. > > > > In short, applications are doing things like: > > > > response

Re: Applications setting connection specific HTTP headers

Am 2021-02-03 um 13:03 schrieb Mark Thomas: Hi all, We have an open PR related to this for HTTP/2 (#277) and I am seeing related issues at $work with HTTP. In short, applications are doing things like: response.setHeader("Transfer-Encoding", "chunked"); which, as you'd expect is causing probl

RE: Question

Thank you so much Mark!!! Yesterday was a PEBKAC day. Sent with BlackBerry Work (www.blackberry.com) From: Mark Thomas Sent: Feb 4, 2021 1:57 AM To: dev@tomcat.apache.org Subject: Re: Question On 04/02/2021 05:04, jonmcalexan...@wellsfargo.com.INVALID wrote: > H

Re: Applications setting connection specific HTTP headers

On 04/02/2021 15:33, Christopher Schultz wrote: > Mark, > > On 2/4/21 8:52 AM, Mark Thomas wrote: >> On 04/02/2021 13:28, Christopher Schultz wrote: >>> I think this should be done in a Valve that is enabled by default, but >>> can be disabled, rendering zero penalty for "well-behaved" application

Re: Applications setting connection specific HTTP headers

Mark, On 2/4/21 8:52 AM, Mark Thomas wrote: > On 04/02/2021 13:28, Christopher Schultz wrote: >> I think this should be done in a Valve that is enabled by default, but >> can be disabled, rendering zero penalty for "well-behaved" applications. >> The Valve can simply wrap the response with a wrapp

Re: [VOTE] Release Apache Tomcat 7.0.108

чт, 28 янв. 2021 г. в 12:49, Violeta Georgieva : > > The proposed Apache Tomcat 7.0.108 release is now available for voting. > > It can be obtained from: > https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.108/ > The Maven staging repo is: > https://repository.apache.org/content/repositor

Re: Applications setting connection specific HTTP headers

On 04/02/2021 13:28, Christopher Schultz wrote: > I think this should be done in a Valve that is enabled by default, but > can be disabled, rendering zero penalty for "well-behaved" applications. > The Valve can simply wrap the response with a wrapper that either prints > an error to the log (maybe

Re: Applications setting connection specific HTTP headers

Mark, On 2/3/21 07:03, Mark Thomas wrote: Hi all, We have an open PR related to this for HTTP/2 (#277) and I am seeing related issues at $work with HTTP. In short, applications are doing things like: response.setHeader("Transfer-Encoding", "chunked"); which, as you'd expect is causing proble

Re: Applications setting connection specific HTTP headers

Le jeu. 4 févr. 2021 à 11:09, Mark Thomas a écrit : > Responses in line: > > On 03/02/2021 19:55, Raymond Auge wrote: > > What about an integration point that acts as a passthrough to such > changes > > that let you "monitor" and/or "defend" against these operations (using > > whatever policy you

[Bug 64938] response.setCharacterEncoding(null) should clear previous charset

https://bz.apache.org/bugzilla/show_bug.cgi?id=64938 Mark Thomas changed: What|Removed |Added Status|NEEDINFO|NEW --- Comment #5 from Mark Thomas ---

Re: Applications setting connection specific HTTP headers

Responses in line: On 03/02/2021 19:55, Raymond Auge wrote: > What about an integration point that acts as a passthrough to such changes > that let you "monitor" and/or "defend" against these operations (using > whatever policy you wish). > The default would be no-op. That certainly provides most

[tomcat] branch 9.0.x updated: Cleanups

This is an automated email from the ASF dual-hosted git repository. remm pushed a commit to branch 9.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/9.0.x by this push: new 04f3694 Cleanups 04f3694 is described below commit

[tomcat] branch master updated: Cleanups

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 fb63c2c Cleanups fb63c2c is described below comm

Re: [VOTE] Release Apache Tomcat 7.0.108

On Thu, Jan 28, 2021 at 10:49 AM Violeta Georgieva wrote: > The proposed Apache Tomcat 7.0.108 release is now available for voting. > > It can be obtained from: > https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.108/ > The Maven staging repo is: > https://repository.apache.org/content/

[Bug 62224] SafeForkJoinWorkerThreadFactory breaks class loading on org.apache.naming.java.javaURLContextFactory

https://bz.apache.org/bugzilla/show_bug.cgi?id=62224 Mark Thomas changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED