bneradt commented on issue #12244: URL: https://github.com/apache/trafficserver/issues/12244#issuecomment-5784113710
This was fixed by #12906 (thanks @JakeChampion), which is in 10.2.0 and master. It never referenced this issue, so the issue stayed open. The `skip_bytes` value in the reports is the size of a forwarded 1xx response. 103 Early Hints go through the same interim-response path as 100 Continue, and that path sets `client_response_hdr_bytes`. Next, a Range miss with `proxy.config.http.cache.range.write` enabled installs the range transform and caches the untransformed 308. The server-to-transform buffer holds only the body, but before #12906 the cache-write consumer was still told to skip the stale 1xx header size, so a 65 byte body tripped `c->skip_bytes <= c->buffer_reader->read_avail()`. #13715 adds a regression test for this scenario: 103 Early Hints, then a 65 byte cacheable 308, requested with `Range: bytes=0-64`. With #12906 backed out, it hits the same assertion reported here; with #12906, ATS keeps running. A 9.2.x backport of #12906 plus the test will follow. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
