Cache-control

[pillarjs]

Cache-control

[dougwilson]

Hi, what about option to clean Cache-control on 206 and 304 responses?

I looked into this and it seems like having them on those responses are valid. Can you explain why you need to clean them for me?

nginx cache they and will send 206 instead 200 on every requests for example.

I'm not sure what this means, can you explain? I use nginx cache in front of this module and it has no issues with the Cache-Control header being there.

or just 'post-header event', to clean it without setHeader overriding.

That is beyond the scope of this module. You'll want to use something like https://www.npmjs.org/package/on-headers#readme :

onHeaders(res, function(){
  if (this.statusCode === 206 || this.statusCode === 304) {
    this.removeHeader('Cache-Control')
  }
})

send(req, url).pipe(res)

[romankoblov]

If you have nginx or cdn with nginx on front with cache and first request response is 206 or 304, it will cache it to url and next users will get that cache instead 200. There is settings in nginx to cache only 200 responses, but then it will cache all 200 pages even if there is no cache-control. Anyway, I re-read RFC, and Cache-Control should be set on 304 responses, so need to use other way to not cache these responses on nginx.