Closed BurhanDanger closed 6 years ago
This is actually an upstream deployment bug (and possibly a regression).
[tw-mbp-zbuhman ~]$ curl -D- https://ptpb.pw/KT9s
HTTP/1.1 404 NOT FOUND
Server: openresty/1.13.6.2
Date: Thu, 16 Aug 2018 17:17:41 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 18
Connection: keep-alive
Vary: Accept
ETag: "paste-5afca108921db93306efb8ad002ffbf42ec867b6"
Cache-Control: max-age=43200, public
X-Varnish: 6661816
Age: 0
Via: 1.1 varnish-v4
status: not found
The problem here is pb told varnish that the response is cacheable, and varnish caches the 404 accordingly. sunset
and/or pbpst
's involvement in this is a red herring.
I had thought this was being handled correctly as of years ago, but clearly it is not.
I mostly use pbpst with sunset and almost never with curl and pb which is why I made misleading conclusion. Since it's pb deployment problem , I'm going to close it now.
Similar to https://github.com/ptpb/pb/issues/217#issue-324746250
Steps To reproduce: