[Bug 66209] CPU regression when classpath Bloom filters are active

https://bz.apache.org/bugzilla/show_bug.cgi?id=66209 --- Comment #13 from Rahul Jaisimha --- I'm worried that adding a new switch on WebResourceRoot that depends on the old switch on Context (for backwards-compatibility) could confuse the config for applications -- You are receiving this mail b

[Bug 66209] CPU regression when classpath Bloom filters are active

https://bz.apache.org/bugzilla/show_bug.cgi?id=66209 Rahul Jaisimha changed: What|Removed |Added CC||jaisi...@amazon.com -- You are recei

[Bug 66240] "Invalid octet [-1]. The valid range for IPv4 octets is 0 to 255." error when subdomain is 4294967295

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

[Bug 66240] "Invalid octet [-1]. The valid range for IPv4 octets is 0 to 255." error when subdomain is 4294967295

https://bz.apache.org/bugzilla/show_bug.cgi?id=66240 --- Comment #3 from Han Li --- Thanks for the feedback. Fixed in: - 10.1.x for 10.1.0-M18 onwards - 10.0.x for 10.0.24 onwards - 9.0.x for 9.0.66 onwards - 8.5.x for 8.5.83 onwards -- You are receiving this mail because: You are the assignee

[GitHub] [tomcat] aooohan closed pull request #548: Avoid int overflow when parsing octet

aooohan closed pull request #548: Avoid int overflow when parsing octet URL: https://github.com/apache/tomcat/pull/548 -- 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. To unsubs

[GitHub] [tomcat] aooohan commented on pull request #548: Avoid int overflow when parsing octet

aooohan commented on PR #548: URL: https://github.com/apache/tomcat/pull/548#issuecomment-1230336825 Thanks for the PR. I applied this manually so I could: - add some test cases - add changelog entry -- This is an automated message from the Apache Git Service. To respond to th

[tomcat] branch 8.5.x updated: Manually merge #548 - Avoid int overflow when parsing octet

This is an automated email from the ASF dual-hosted git repository. lihan 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 44263ecce6 Manually merge #548 - Avoid int overflow

[tomcat] branch 9.0.x updated: Manually merge #548 - Avoid int overflow when parsing octet

This is an automated email from the ASF dual-hosted git repository. lihan 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 d855bc1c99 Manually merge #548 - Avoid int overflow

[tomcat] branch main updated: Manually merge #548 - Avoid int overflow when parsing octet

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 054abe0fab Manually merge #548 - Avoid int overflow w

[tomcat] branch 10.0.x updated: Manually merge #548 - Avoid int overflow when parsing octet

This is an automated email from the ASF dual-hosted git repository. lihan 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 fb4d9198de Manually merge #548 - Avoid int overfl

Re: [tomcat] branch main updated: Improve handling of EL error messages.

Mark, On 8/29/22 02:39, ma...@apache.org wrote: 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 e

[GitHub] [tomcat] sashashura commented on pull request #549: GitHub Workflows security hardening

sashashura commented on PR #549: URL: https://github.com/apache/tomcat/pull/549#issuecomment-1230174757 Great. There is no way for me to see if this is set in the org settings. In this case I still think it still adds a little value of portability if transferred to other repository and impr

[GitHub] [tomcat] markt-asf closed pull request #549: GitHub Workflows security hardening

markt-asf closed pull request #549: GitHub Workflows security hardening URL: https://github.com/apache/tomcat/pull/549 -- 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. To unsubs

[GitHub] [tomcat] markt-asf commented on pull request #549: GitHub Workflows security hardening

markt-asf commented on PR #549: URL: https://github.com/apache/tomcat/pull/549#issuecomment-1230114372 Unnecessary. Handled by org level permissions. -- 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

[GitHub] [tomcat] sashashura opened a new pull request, #549: GitHub Workflows security hardening

sashashura opened a new pull request, #549: URL: https://github.com/apache/tomcat/pull/549 This PR adds explicit [permissions section](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions) to workflows. This is a security best practice because by