You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by GitBox <gi...@apache.org> on 2020/10/13 15:04:20 UTC

[GitHub] [trafficserver] zwoop opened a new issue #7272: Regression: serve stale content when server closes the connection

zwoop opened a new issue #7272:
URL: https://github.com/apache/trafficserver/issues/7272


   There's a newish test in the cache-test suit, which looks like it's triggering a bug related to TE: and chunking, with stale content. It works fine in v7.x and 9.x (and master), but hangs the client in 8.0.x and 8.1.x. 8.1.x has the fixes from 788224fd35c714ce89c23922ce9d9f770db25ea4, but that doesn't help here, so there must be something else fixed in 9.0.x that's not been back ported to 8.1.x
   
   
   ```
   root@jenkins 503/0 # npm run --silent cli --base=http://127.0.0.1:8080 --id=stale-close
   Running stale-close
   === Client request 1
       GET http://127.0.0.1:8080/test/259d568f-92d7-440a-8c85-08a382eef418
       Pragma: foo
       Cache-Control: nothing-to-see-here
       Test-Name: Does HTTP cache serve stale content when server closes the connection?
       Test-ID: stale-close
       Req-Num: 1
   
   === Client response 1
       HTTP 200 OK
       age: 0
       cache-control: max-age=2
       capability-seen:
       client-request-count: 1
       connection: close
       content-length: 36
       content-type: text/plain
       date: Tue, 13 Oct 2020 15:00:23 GMT
       request-numbers: 1
       server: ATS/8.1.1
       server-base-url: /test/259d568f-92d7-440a-8c85-08a382eef418
       server-now: 1602601223539
       server-request-count: 1
   
   === Client request 2
       GET http://127.0.0.1:8080/test/259d568f-92d7-440a-8c85-08a382eef418
       Pragma: foo
       Cache-Control: nothing-to-see-here
       Test-Name: Does HTTP cache serve stale content when server closes the connection?
       Test-ID: stale-close
       Req-Num: 2
   
   === Client response 2
       HTTP 200 OK
       age: 3
       cache-control: max-age=2
       capability-seen:
       client-request-count: 1
       connection: close
       content-type: text/plain
       date: Tue, 13 Oct 2020 15:00:23 GMT
       request-numbers: 1
       server: ATS/8.1.1
       server-base-url: /test/259d568f-92d7-440a-8c85-08a382eef418
       server-now: 1602601223539
       server-request-count: 1
       transfer-encoding: chunked
       warning: 111 ApacheTrafficServer/8.1.1
   
   ==== Results
   🔹 - Response body is "", not "259d568f-92d7-440a-8c85-08a382eef418"
   ```
   
   Note that the response body here is "", because the server (or client) times out after a long time.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [trafficserver] zwoop commented on issue #7272: Regression: serve stale content when server closes the connection

Posted by GitBox <gi...@apache.org>.
zwoop commented on issue #7272:
URL: https://github.com/apache/trafficserver/issues/7272#issuecomment-709697371


   @vmamidi tracked down the missing fix from 9.0.x to https://github.com/apache/trafficserver/pull/5868 . I'm not 100% sure how we broke it into 8, but this is now fixed in 8.1.1.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [trafficserver] zwoop closed issue #7272: Regression: serve stale content when server closes the connection

Posted by GitBox <gi...@apache.org>.
zwoop closed issue #7272:
URL: https://github.com/apache/trafficserver/issues/7272


   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org