[GitHub] [tomcat] markt-asf closed pull request #558: It is time to stop using absolute redirects

markt-asf closed pull request #558: It is time to stop using absolute redirects URL: https://github.com/apache/tomcat/pull/558 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. T

[GitHub] [tomcat] markt-asf commented on pull request #558: It is time to stop using absolute redirects

markt-asf commented on PR #558: URL: https://github.com/apache/tomcat/pull/558#issuecomment-1286536223 `useRelativeRedirects` is already `true` by default. However, the Servlet specification *requires* (see section 5.5) that Tomcat uses absolute redirects. Therefore, if `STRICT_SERVLET_COMP

[Bug 66318] Set multiple domain names for one address，In Windows 10 OS. AbstractProcessor.populateRequestAttributeRemoteHost aways get wrong host

https://bz.apache.org/bugzilla/show_bug.cgi?id=66318 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED OS|

[Bug 66318] New: Set multiple domain names for one address，In Windows 10 OS. AbstractProcessor.populateRequestAttributeRemoteHost aways get wrong host

https://bz.apache.org/bugzilla/show_bug.cgi?id=66318 Bug ID: 66318 Summary: Set multiple domain names for one address，In Windows 10 OS. AbstractProcessor.populateRequestAttributeRemoteHost aways get wrong host

[GitHub] [tomcat] eperez commented on pull request #558: It is time to stop using absolute redirects

eperez commented on PR #558: URL: https://github.com/apache/tomcat/pull/558#issuecomment-1286470026 > Why? Is there a reason or a source you can refer to? It has passed some years now since this design mistake was fixed: https://www.rfc-editor.org/rfc/rfc7231#section-7.1.2 Keeping

[GitHub] [tomcat] aooohan commented on pull request #558: It is time to stop using absolute redirects

aooohan commented on PR #558: URL: https://github.com/apache/tomcat/pull/558#issuecomment-1286369013 Why? Is there a reason or a source you can refer to? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to

[GitHub] [tomcat] aooohan commented on a diff in pull request #556: Note that maxHttpHeaderSize always allocates the max size

aooohan commented on code in PR #556: URL: https://github.com/apache/tomcat/pull/556#discussion_r1001286110 ## webapps/docs/config/http.xml: ## @@ -525,6 +525,11 @@ the request line, header names and header values. If not specified, this attribute is set to the val

Buildbot success in on tomcat-10.1.x

Build status: Build succeeded! Worker used: bb2_worker2_ubuntu URL: https://ci2.apache.org/#builders/44/builds/551 Blamelist: Mark Thomas , lihan Build Text: build successful Status Detected: restored build Build Source Stamp: [branch 10.1.x] 4defd829c3044358f4a7746ede4248e30d35d73e Steps: wo

[tomcat] branch 8.5.x updated: Populate min Java version at build time

This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch 8.5.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/8.5.x by this push: new d82e231a89 Populate min Java version at build time

[tomcat] branch 9.0.x updated: Populate min Java version at build time

This is an automated email from the ASF dual-hosted git repository. markt 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 9d21c29144 Populate min Java version at build time

[tomcat] branch main updated (d95b769b4f -> d27c63055a)

This is an automated email from the ASF dual-hosted git repository. markt pushed a change to branch main in repository https://gitbox.apache.org/repos/asf/tomcat.git from d95b769b4f Fix Javadoc related build failure when building with Java 19 add d27c63055a Populate min Java version at

[tomcat] branch 10.1.x updated: Populate min Java version at build time

This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch 10.1.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/10.1.x by this push: new 4defd829c3 Populate min Java version at build tim

Re: [DISCUSS] EOL date for 8.5.x

On Fri, Oct 7, 2022 at 5:28 AM Mark Thomas wrote: > Hi all, > > I don't think there is a need to make a decision on this quickly, but > based on past experience and the current discussions about Jakarta EE 11 > I think this is something we need to start thinking about. > > Some key facts: > > - T

Buildbot failure in on tomcat-10.1.x

Build status: BUILD FAILED: failed compile (failure) Worker used: bb2_worker2_ubuntu URL: https://ci2.apache.org/#builders/44/builds/550 Blamelist: Mark Thomas , lihan Build Text: failed compile (failure) Status Detected: new failure Build Source Stamp: [branch 10.1.x] 11807d6958125b96c976bad4f779

Re: [DISCUSS] EOL date for 8.5.x

> 2022年10月20日 17:01，Rémy Maucherat 写道： > > On Fri, Oct 7, 2022 at 11:28 AM Mark Thomas > wrote: >> >> Hi all, >> >> I don't think there is a need to make a decision on this quickly, but >> based on past experience and the current discussions about Jakarta EE 11 >> I

[Bug 66317] AccessControlException on EL 5.0

https://bz.apache.org/bugzilla/show_bug.cgi?id=66317 Han Li changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[GitHub] [tomcat] aooohan closed pull request #557: Fix for Lambda coercion security manager missing privileges

aooohan closed pull request #557: Fix for Lambda coercion security manager missing privileges URL: https://github.com/apache/tomcat/pull/557 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the speci

[tomcat] branch 9.0.x updated: Fix Javadoc related build failure when building with Java 19

This is an automated email from the ASF dual-hosted git repository. markt 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 1d3e328723 Fix Javadoc related build failure when b

[GitHub] [tomcat] aooohan commented on pull request #557: Fix for Lambda coercion security manager missing privileges

aooohan commented on PR #557: URL: https://github.com/apache/tomcat/pull/557#issuecomment-1285610031 Thank for the PR. I applied this manually so I could: - add a change log entry - slightly optimize code writing Fixed in: - 11.0.x for 11.0.0-M1 onwoards - 10.1.x f

[tomcat] branch 8.5.x updated: Fix Javadoc related build failure when building with Java 19

This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch 8.5.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/8.5.x by this push: new 70a07e03cd Fix Javadoc related build failure when b

[tomcat] branch 10.1.x updated: Fix Javadoc related build failure when building with Java 19

This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch 10.1.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/10.1.x by this push: new 11807d6958 Fix Javadoc related build failure when

[tomcat] branch main updated: Fix Javadoc related build failure when building with Java 19

This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/main by this push: new d95b769b4f Fix Javadoc related build failure when bui

[tomcat] branch 10.1.x updated: Fix for Lambda coercion security manager missing privileges.

This is an automated email from the ASF dual-hosted git repository. lihan pushed a commit to branch 10.1.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/10.1.x by this push: new 220c2af01e Fix for Lambda coercion security manag

Re: [tomcat] branch loom created (now 6a22f2f399)

On Thu, Oct 20, 2022 at 11:28 AM Mark Thomas wrote: > > On 20/10/2022 09:32, Rémy Maucherat wrote: > > > > > This is interesting since now is the best time to discuss long term plans. > > > > We'll see if there are some scheduling gains with Loom ... But I don't > > think thread scheduling was th

[tomcat] branch main updated: Fix for Lambda coercion security manager missing privileges.

This is an automated email from the ASF dual-hosted git repository. lihan pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/main by this push: new 34a48511a5 Fix for Lambda coercion security manager m

[Bug 66317] AccessControlException on EL 5.0

https://bz.apache.org/bugzilla/show_bug.cgi?id=66317 --- Comment #2 from Isaac Rivera Rivas --- Proposed fix for this https://github.com/apache/tomcat/pull/557 -- You are receiving this mail because: You are the assignee for the bug. -

[GitHub] [tomcat] isaacrivriv opened a new pull request, #557: Fix for Lambda coercion security manager missing privileges

isaacrivriv opened a new pull request, #557: URL: https://github.com/apache/tomcat/pull/557 Fix for https://bz.apache.org/bugzilla/show_bug.cgi?id=66317 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to

Re: [tomcat] branch loom created (now 6a22f2f399)

On 20/10/2022 09:32, Rémy Maucherat wrote: This is interesting since now is the best time to discuss long term plans. We'll see if there are some scheduling gains with Loom ... But I don't think thread scheduling was the problem in Tomcat. Maybe lock concurrency but it seems these had been el

Re: [DISCUSS] EOL date for 8.5.x

Am 20.10.2022 um 11:01 schrieb Rémy Maucherat: On Fri, Oct 7, 2022 at 11:28 AM Mark Thomas wrote: Hi all, I don't think there is a need to make a decision on this quickly, but based on past experience and the current discussions about Jakarta EE 11 I think this is something we need to start t

Re: [DISCUSS] EOL date for 8.5.x

On Fri, Oct 7, 2022 at 11:28 AM Mark Thomas wrote: > > Hi all, > > I don't think there is a need to make a decision on this quickly, but > based on past experience and the current discussions about Jakarta EE 11 > I think this is something we need to start thinking about. > > Some key facts: > > -

Re: [DISCUSS] EOL date for 8.5.x

Bump. On 07/10/2022 10:27, Mark Thomas wrote: Hi all, I don't think there is a need to make a decision on this quickly, but based on past experience and the current discussions about Jakarta EE 11 I think this is something we need to start thinking about. Some key facts: - Tomcat 7.0.x re

Re: [tomcat] branch loom created (now 6a22f2f399)

Hi Mark, On Wed, Oct 19, 2022 at 4:41 PM Mark Thomas wrote: > > On 19/10/2022 15:39, ma...@apache.org wrote: > > This is an automated email from the ASF dual-hosted git repository. > > > > markt pushed a change to branch loom > > in repository https://gitbox.apache.org/repos/asf/tomcat.git > > So