Twitter

@caddyserver @srfrolov Wow @caddyserver . Now you "only" need to add black- / white-list Syntax and you are another… https://t.co/0FYeCXzept
Thursday, August 17, 2017 - 09:52
@varnishcache 4. Or I could create a new GET endpoint on our API with /exists or something that acts like HEAD does.
Wednesday, August 16, 2017 - 16:47
@varnishcache 3. I could just suck it up an process all those unnecessary GETs on the server.
Wednesday, August 16, 2017 - 16:46
@varnishcache 2. It is an API for our app, so I could just send the requests straight to the origin from the client.
Wednesday, August 16, 2017 - 16:45
@varnishcache 1. have Varnish pass all HEADs to the origin.
Wednesday, August 16, 2017 - 16:44
.@varnishcache converts HEAD requests to GET, but our HEAD requests are far more frequent and efficient than GET. Possible solutions 1/
Wednesday, August 16, 2017 - 16:43
@dbu @varnishcache Yeah, I figured it out. It kind of sucks for our use case, though.
Wednesday, August 16, 2017 - 14:27
@karptonite @varnishcache varnish always sends GET when its cache is not useable. when useable, it responds to the client HEAD request
Wednesday, August 16, 2017 - 10:27
@varnishcache So I guess I shouldn’t have gone to the trouble of processing them separately? When GET is more expensive than HEAD?
Wednesday, August 16, 2017 - 02:17
And an hour later… apparently @varnishcache doesn’t send HEAD requests to the back end, sending GET instead…. 1/
Wednesday, August 16, 2017 - 02:16

Pages