[ https://issues.apache.org/jira/browse/TS-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507508#comment-13507508 ]
Rob Lyon commented on TS-1086: ------------------------------ I am seeing the same issue. I am seeing it on about 5% of the requests. The bad response (TCP_REFRESH_HIT/304) appears to be paired with a correct response (TCP_REFRESH_HIT/200) in the same second. The Via header is confirming a unconditional request (simple): ApacheTrafficServer/3.2.0 [uScSsNf pNeN:t cCSi p sS]. > Returning 304 response to unconditional request > ----------------------------------------------- > > Key: TS-1086 > URL: https://issues.apache.org/jira/browse/TS-1086 > Project: Traffic Server > Issue Type: Bug > Components: HTTP > Affects Versions: 3.0.1 > Environment: Observed on Amazon/ec2 build, which is 3.0.1 on > redhat-like linux. > Reporter: Nick Kew > Fix For: 3.3.1 > > > ab is reporting HTTP 304 responses to a small number of unconditional > requests in a test run: > GET /testfile.html HTTP/1.0^M > Host: localhost^M > User-Agent: ApacheBench/2.3^M > Accept: */*^M > ^M > HTTP/1.0 304 Not Modified^M > Date: Mon, 21 Nov 2011 14:23:48 GMT^M > Server: ATS/3.0.1^M > ETag: "5e24-24cd-4b23b69f6e89c"^M > Cache-Control: max-age=60^M > Age: 2^M > ^M > I presume what's happening is that trafficserver is sending a conditional > request with If-Modified-Since to the origin server, and then returning the > origin's 304 response to the client's unconditional request. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira