[Bug 62072] Add support for request compression

https://bz.apache.org/bugzilla/show_bug.cgi?id=62072 --- Comment #5 from Matafagafo --- Today I tried to use Apache HttpClient GzipCompressingEntity (https://hc.apache.org/httpcomponents-client-4.5.x/current/httpclient/apidocs/org/apache/http/client/entity/GzipCompressingEntity.html) to send

[tomcat] branch master updated: Add logging to help debug GitHub CI failures

This is an automated email from the ASF dual-hosted git repository. markt 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 6e3a234 Add logging to help debug GitHub CI

[GitHub] [tomcat] markt-asf commented on pull request #405: docs: fix spelling

markt-asf commented on pull request #405: URL: https://github.com/apache/tomcat/pull/405#issuecomment-784271485 These schema do not originate in the Apache Tomcat project. The best place to fix them would at source. The Jakarta EE schema can be found at:

[GitHub] [tomcat] markt-asf closed pull request #405: docs: fix spelling

markt-asf closed pull request #405: URL: https://github.com/apache/tomcat/pull/405 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

[Bug 62072] Add support for request compression

https://bz.apache.org/bugzilla/show_bug.cgi?id=62072 Matafagafo changed: What|Removed |Added CC||matafag...@yahoo.com -- You are

[Bug 64762] CoyoteInputStream getInputStream() read (wait after premature end and the rest comes)

https://bz.apache.org/bugzilla/show_bug.cgi?id=64762 Mark Thomas changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|---

[Bug 64771] Windows CPU processor always running by a thread reading request body from https connection

https://bz.apache.org/bugzilla/show_bug.cgi?id=64771 --- Comment #13 from Mark Thomas --- As per the update to the spring issue (https://github.com/spring-projects/spring-framework/issues/26407) 9.0.x now contains a fix that may help with this. Currently waiting for user feedback. -- You are

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

https://bz.apache.org/bugzilla/show_bug.cgi?id=64938 --- Comment #6 from Mark Thomas --- I've implemented the changes agreed in the Jakarta Servlet project for 10.0.x. They will be in 10.0.3 onwards. I have started a discussion on the dev@ list to determine if the changes should be back-ported

Re: [tomcat] branch master updated: Fix BZ 64938 Clarify expected behaviour of setCharacterEncoding(null)

On 23/02/2021 12:50, ma...@apache.org wrote: > This is an automated email from the ASF dual-hosted git repository. > > markt 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

[tomcat] branch master updated: Fix BZ 64938 Clarify expected behaviour of setCharacterEncoding(null)

This is an automated email from the ASF dual-hosted git repository. markt 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 5e974d6 Fix BZ 64938 Clarify expected behaviour