Am I reading the origin headers correctly -- that they are sending "no-cache", eg, please ask the origin every time if its ok to send the current object? Can you ask them to stop sending that and see if that changes behavior? (Also, no-cache doesn't take any arguments, so the ="set-cookie" part is a waste of bits.
On Sun, Feb 24, 2019 at 6:46 AM ezko <[email protected]> wrote: > > Hi, > we are using ATS 7.1.6 for live HLS reverse proxy. we have ~6K clients > hitting the same playlist and segments at the same time. > we enabled collapse forwarding plugin with RWW, and it seems to work really > nice for the segments. > > But for the playlists (see example below) we are seeing leakage of IMS > requests to the origin (we are seeing many 304 responses from the origin) > > It look like collapse forwarding doesn't kick in in case of IMS. Is this > true ? > How can we prevent leakage of IMS requests to the origin ? > Thanks, > Erez > > < HTTP/1.1 200 OK > < Accept-Ranges: bytes > < Access-Control-Allow-Origin: * > < Access-Control-Expose-Headers: Date > < Content-Type: application/vnd.apple.mpegurl > < Content-Length: 835 > < Cache-Control: max-age=1 > < Cache-Control: public > < Cache-Control: no-cache="set-cookie" > < Date: Sun, 24 Feb 2019 10:24:12 GMT > < Etag: "5c7270c9-343" > < Expires: Sun, 24 Feb 2019 10:24:13 GMT > < Last-Modified: Sun, 24 Feb 2019 10:24:09 GMT > < Vary: Accept-Encoding > < Age: 0 > < Connection: keep-alive > < Via: http/1.1 vds-cache (ApacheTrafficServer/7.1.6 [uScRs f p eN:t cCHi p > s ]) > < Server: ATS/7.1.6 > < > > > > -- > Sent from: http://apache-traffic-server.24303.n7.nabble.com/
