This is an automated email from the ASF dual-hosted git repository.
markt-asf pushed a commit to branch 11.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/11.0.x by this push:
new e07b0af29c Clean-up - no functional change
e07b0af29c is described below
commit e07b0af29c0b6ba4ef342495e44d006a70eb65ea
Author: Mark Thomas <[email protected]>
AuthorDate: Tue Sep 29 16:38:28 2026 +0100
Clean-up - no functional change
---
java/org/apache/coyote/http11/Http11Processor.java | 20 +++++++++++---------
1 file changed, 11 insertions(+), 9 deletions(-)
diff --git a/java/org/apache/coyote/http11/Http11Processor.java
b/java/org/apache/coyote/http11/Http11Processor.java
index 76fcb3482a..aceec7e198 100644
--- a/java/org/apache/coyote/http11/Http11Processor.java
+++ b/java/org/apache/coyote/http11/Http11Processor.java
@@ -161,7 +161,7 @@ public class Http11Processor extends AbstractProcessor {
* Creates a new HTTP/1.1 processor.
*
* @param protocol the protocol handler
- * @param adapter the adapter to pass requests to
+ * @param adapter the adapter to pass requests to
*/
public Http11Processor(AbstractHttp11Protocol<?> protocol, Adapter
adapter) {
super(adapter);
@@ -349,7 +349,10 @@ public class Http11Processor extends AbstractProcessor {
Request upgradeRequest = null;
try {
upgradeRequest = cloneRequest(request);
- // Make sure any remaining body is swallowed
before we start processing the upgraded protocol
+ /*
+ * Make sure any remaining body is swallowed
before we start processing the upgraded
+ * protocol.
+ */
inputBuffer.endRequest();
} catch (ByteChunk.BufferOverflowException ioe) {
response.setStatus(HttpServletResponse.SC_REQUEST_ENTITY_TOO_LARGE);
@@ -1151,13 +1154,12 @@ public class Http11Processor extends AbstractProcessor {
protected boolean flushBufferedWrite() throws IOException {
if (outputBuffer.hasDataToWrite()) {
if (outputBuffer.flushBuffer(false)) {
- // The buffer wasn't fully flushed so re-register the
- // socket for write. Note this does not go via the
- // Response since the write registration state at
- // that level should remain unchanged. Once the buffer
- // has been emptied then the code below will call
- // Adaptor.asyncDispatch() which will enable the
- // Response to respond to this event.
+ /*
+ * The buffer wasn't fully flushed so re-register the socket
for write. Note this does not go via the
+ * Response since the write registration state at that level
should remain unchanged. Once the buffer
+ * has been emptied then the code below will call
Adaptor.asyncDispatch() which will enable the Response
+ * to respond to this event.
+ */
outputBuffer.registerWriteInterest();
return true;
}
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
