masaori335 opened a new pull request, #12257: URL: https://github.com/apache/trafficserver/pull/12257
# Problem Recently, we found that some clients send `HEADERS` frame followed by an empty `DATA` frame with the `END_STREAM` flag even for GET requests. - `HEADERS` frame with `END_HEADERS` flag - zero-length `DATA` frame with `END_STREAM` flag Sometimes ATS closes the stream immediately after it sends DATA frame to the client, right after handling the `HEADERS` frame. In this case, ATS treats the zero-length DATA frame as a stream error because the stream is already closed. However, this appears to be a bug. The spec[*1] says that an endpoint should keep the stream in the `half-closed (local)` state after sending `END_STREAM` flag and wait to receive `END_STREAM` flag from the peer before closing it. With this change, ATS waits for the `END_STREAM` flag until the `http.transaction_no_activity_timeout_in` expires. [*1] https://datatracker.ietf.org/doc/html/rfc9113#name-stream-states -- 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 unsubscribe, e-mail: github-unsubscr...@trafficserver.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
