[GitHub] [tomcat] CrazyHZM opened a new pull request, #502: Support max http request header size and max http header size configuration separation

CrazyHZM opened a new pull request, #502: URL: https://github.com/apache/tomcat/pull/502 Mail link：https://bz.apache.org/bugzilla/show_bug.cgi?id=65866 -- 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] CrazyHZM commented on pull request #501: Support max http request header size and max http header size configuration separation

CrazyHZM commented on PR #501: URL: https://github.com/apache/tomcat/pull/501#issuecomment-1094629380 > That seems pretty straightforward. I'm slightly skeptical about the real practical use since trying to optimize the sizes too much is risky, but no problem, this is the user's

[tomcat] branch 9.0.x updated: Minor typo on javadoc of setHostHeader method

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 fa4aaf0b18 Minor typo on javadoc of setHostHeader

[GitHub] [tomcat] gmshake commented on a diff in pull request #501: Support max http request header size and max http header size configuration separation

gmshake commented on code in PR #501: URL: https://github.com/apache/tomcat/pull/501#discussion_r847041315 ## java/org/apache/coyote/http11/AbstractHttp11Protocol.java: ## @@ -244,6 +244,34 @@ public void setMaxSavePostSize(int maxSavePostSize) { public void

[tomcat] branch 10.0.x updated (3df462befe -> 89cdabc442)

This is an automated email from the ASF dual-hosted git repository. remm pushed a change to branch 10.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git from 3df462befe PR#494: Fix native library location add 89cdabc442 Minor typo on javadoc of setHostHeader method No

[tomcat] branch 8.5.x updated: Minor typo on javadoc of setHostHeader method

This is an automated email from the ASF dual-hosted git repository. remm 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 4c7f21cd0c Minor typo on javadoc of setHostHeader

[GitHub] [tomcat] rmaucher commented on pull request #501: Support max http request header size and max http header size configuration separation

rmaucher commented on PR #501: URL: https://github.com/apache/tomcat/pull/501#issuecomment-1094815675 The proposed patch is still simpler and should work well, so I will merge that one. -- This is an automated message from the Apache Git Service. To respond to the message, please log on

[GitHub] [tomcat] rmannibucau commented on pull request #501: Support max http request header size and max http header size configuration separation

rmannibucau commented on PR #501: URL: https://github.com/apache/tomcat/pull/501#issuecomment-1094636457 +1 I see two advantages: 1. enables cases where "front" tomcat has big incoming headers but "normal" forwarded headers 2. enables better web server abstractions which often

[GitHub] [tomcat] gmshake commented on a diff in pull request #501: Support max http request header size and max http header size configuration separation

gmshake commented on code in PR #501: URL: https://github.com/apache/tomcat/pull/501#discussion_r847041315 ## java/org/apache/coyote/http11/AbstractHttp11Protocol.java: ## @@ -244,6 +244,34 @@ public void setMaxSavePostSize(int maxSavePostSize) { public void

[GitHub] [tomcat] rmaucher commented on pull request #501: Support max http request header size and max http header size configuration separation

rmaucher commented on PR #501: URL: https://github.com/apache/tomcat/pull/501#issuecomment-1094622549 That seems pretty straightforward. I'm slightly skeptical about the real practical use since trying to optimize the sizes too much is risky, but no problem, this is the user's

[GitHub] [tomcat] CrazyHZM commented on a diff in pull request #501: Support max http request header size and max http header size configuration separation

CrazyHZM commented on code in PR #501: URL: https://github.com/apache/tomcat/pull/501#discussion_r847005884 ## java/org/apache/coyote/http11/AbstractHttp11Protocol.java: ## @@ -244,6 +244,34 @@ public void setMaxSavePostSize(int maxSavePostSize) { public void

[GitHub] [tomcat] gmshake commented on a diff in pull request #501: Support max http request header size and max http header size configuration separation

gmshake commented on code in PR #501: URL: https://github.com/apache/tomcat/pull/501#discussion_r847041315 ## java/org/apache/coyote/http11/AbstractHttp11Protocol.java: ## @@ -244,6 +244,34 @@ public void setMaxSavePostSize(int maxSavePostSize) { public void

[Bug 57611] Update Bugzilla URL in documentation, site, etc.

https://bz.apache.org/bugzilla/show_bug.cgi?id=57611 --- Comment #2 from Jason Adams --- (In reply to Konstantin Kolinko from comment #0) > About a week ago the ASF Bugzilla was migrated to a new, separate host. As a > result, the issue URLs have changed from > >

[Bug 65866] Allow AbstractHttp11Protocol.setMaxHttpHeaderSize to apply to request or response only

https://bz.apache.org/bugzilla/show_bug.cgi?id=65866 --- Comment #3 from Zhongming Hua --- Please review the code first, if there is no problem, I will support this on other branches as well. https://github.com/apache/tomcat/pull/501 -- You are receiving this mail because: You are the assignee

[GitHub] [tomcat] gmshake commented on a diff in pull request #501: Support max http request header size and max http header size configuration separation

gmshake commented on code in PR #501: URL: https://github.com/apache/tomcat/pull/501#discussion_r846991658 ## java/org/apache/coyote/http11/AbstractHttp11Protocol.java: ## @@ -244,6 +244,34 @@ public void setMaxSavePostSize(int maxSavePostSize) { public void

Re: [Bug 57611] Update Bugzilla URL in documentation, site, etc.

On 11/04/2022 09:10, bugzi...@apache.org wrote: https://bz.apache.org/bugzilla/show_bug.cgi?id=57611 --- Comment #2 from Jason Adams --- I've disabled this idiot's account and removed the spam. Mark - To unsubscribe,

[GitHub] [tomcat] gmshake commented on pull request #501: Support max http request header size and max http header size configuration separation

gmshake commented on PR #501: URL: https://github.com/apache/tomcat/pull/501#issuecomment-1094800382 > Overall, I prefer the PR as it is right now, it's simpler. If the new setters are used, then the behavior could be slightly different, but since this is new API this should be fine.

[GitHub] [tomcat] CrazyHZM commented on pull request #501: Support max http request header size and max http header size configuration separation

CrazyHZM commented on PR #501: URL: https://github.com/apache/tomcat/pull/501#issuecomment-1094598895 Please review the code first, if there is no problem, I will support this on other branches as well. -- This is an automated message from the Apache Git Service. To respond to the

[GitHub] [tomcat] CrazyHZM opened a new pull request, #501: Support max http request header size and max http header size configuration separation

CrazyHZM opened a new pull request, #501: URL: https://github.com/apache/tomcat/pull/501 Mail link：https://bz.apache.org/bugzilla/show_bug.cgi?id=65866 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL

[GitHub] [tomcat] rmannibucau commented on a diff in pull request #501: Support max http request header size and max http header size configuration separation

rmannibucau commented on code in PR #501: URL: https://github.com/apache/tomcat/pull/501#discussion_r847064940 ## java/org/apache/coyote/http11/AbstractHttp11Protocol.java: ## @@ -244,6 +244,34 @@ public void setMaxSavePostSize(int maxSavePostSize) { public void

[GitHub] [tomcat] rmaucher commented on pull request #501: Support max http request header size and max http header size configuration separation

rmaucher commented on PR #501: URL: https://github.com/apache/tomcat/pull/501#issuecomment-1094743565 Overall, I prefer the PR as it is right now, it's simpler. If the new setters are used, then the behavior could be slightly different, but since this is new API this should be fine. --

[tomcat] branch main updated: PR501: Add header size attributes

This is an automated email from the ASF dual-hosted git repository. remm 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 6cdd999e65 PR501: Add header size attributes

[GitHub] [tomcat] CrazyHZM opened a new pull request, #503: Support max http request header size and max http header size configuration separation

CrazyHZM opened a new pull request, #503: URL: https://github.com/apache/tomcat/pull/503 Mail link：https://bz.apache.org/bugzilla/show_bug.cgi?id=65866 -- 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] CrazyHZM closed pull request #503: Support max http request header size and max http header size configuration separation

CrazyHZM closed pull request #503: Support max http request header size and max http header size configuration separation URL: https://github.com/apache/tomcat/pull/503 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

[tomcat] branch 9.0.x updated: PR501: Add header size attributes

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 431f08b66e PR501: Add header size attributes

[Bug 65866] Allow AbstractHttp11Protocol.setMaxHttpHeaderSize to apply to request or response only

https://bz.apache.org/bugzilla/show_bug.cgi?id=65866 Remy Maucherat changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[GitHub] [tomcat] CrazyHZM closed pull request #502: Support max http request header size and max http header size configuration separation

CrazyHZM closed pull request #502: Support max http request header size and max http header size configuration separation URL: https://github.com/apache/tomcat/pull/502 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

[Bug 66005] New: Apache crashes, if there is a tomcat server, which can not be resolved

https://bz.apache.org/bugzilla/show_bug.cgi?id=66005 Bug ID: 66005 Summary: Apache crashes, if there is a tomcat server, which can not be resolved Product: Tomcat Connectors Version: 1.2.48 Hardware: Other

[GitHub] [tomcat] rmaucher commented on pull request #501: Support max http request header size and max http header size configuration separation

rmaucher commented on PR #501: URL: https://github.com/apache/tomcat/pull/501#issuecomment-1094929661 Merged with changed. I didn't understand the changes to TestHttp2Limits, HTTP/2 should use the new request header size and that should be it. Also updated docs and changelog. -- This is

[Bug 59164] If tomcat server can not be resolved, crash occurred.

https://bz.apache.org/bugzilla/show_bug.cgi?id=59164 Lothar changed: What|Removed |Added Status|RESOLVED|REOPENED Version|1.2.41

[GitHub] [tomcat] CrazyHZM commented on pull request #501: Support max http request header size and max http header size configuration separation

CrazyHZM commented on PR #501: URL: https://github.com/apache/tomcat/pull/501#issuecomment-1094916955 @rmaucher I can patch several other branches, right? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL

[Bug 59164] If tomcat server can not be resolved, crash occurred.

https://bz.apache.org/bugzilla/show_bug.cgi?id=59164 Rainer Jung changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

[tomcat] branch 8.5.x updated: PR501: Add header size attributes

This is an automated email from the ASF dual-hosted git repository. remm 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 5567e2e30e PR501: Add header size attributes

[GitHub] [tomcat] rmaucher closed pull request #501: Support max http request header size and max http header size configuration separation

rmaucher closed pull request #501: Support max http request header size and max http header size configuration separation URL: https://github.com/apache/tomcat/pull/501 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

[tomcat] branch 10.0.x updated: PR501: Add header size attributes

This is an automated email from the ASF dual-hosted git repository. remm pushed a commit to branch 10.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/10.0.x by this push: new de48ef4877 PR501: Add header size attributes

[GitHub] [tomcat] CrazyHZM commented on pull request #501: Support max http request header size and max http header size configuration separation

CrazyHZM commented on PR #501: URL: https://github.com/apache/tomcat/pull/501#issuecomment-1094939842 @rmaucher Do i need to resubmit a clean pr? -- 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

[Bug 65991] NPE in SSLAuthenticator.java:201 if bindOnInit="false"

https://bz.apache.org/bugzilla/show_bug.cgi?id=65991 --- Comment #6 from Amit Pande --- Hello Remy, Running into the same issue even without using bindOnInit as mentioned in comment #4. This is the connector configuration in use.

Native Compilation, Continuation 2022

Hi folks, I'm jumping in on the bandwagon again. Specifically to talk some more about native compilation. The graal compiler is making headway, and it's becoming better and better at native compilation [1]. I'll put some historical context at the bottom of this post for clarity. I have a few