Can Nginx only cache reponse body while excluding some response headers?

[yf chu]

A request is sent from client to nginx, if it did not hit the cache, I hope nginx only caches the response body returned by upstream and send the headers and response body returned by upstream to client.
If the request hit the cache, I hope nginx can generate new headers and send them with the cached response body to client.   








At 2018-12-08 06:23:54, "Francis Daly" <francis at daoine.org> wrote:
>On Sun, Dec 02, 2018 at 06:29:33PM +0800, yf chu wrote:
>
>Hi there,
>
>> We all know that the cache feature in Nginx will cache all response content generated by upstream server. But I wonder whether there is a solution that only the response body is cached by Nginx while some response headers should not be cached and should be sent to client directly .
>
>I'm afraid I don't understand what exactly you are asking.
>
>Could you give more details, or an example?
>
>Such as:
>
>request from client to nginx; not in cache, so nginx asks upstream which
>returns headers+body. What do you want nginx to store in the cache,
>and what should nginx send to the client?
>
>same request from client to nginx; it is in the cache. What should nginx
>send to the client?
>
>The answer to that might make your question clearer.
>
>Thanks,
>
>	f
>-- 
>Francis Daly        francis at daoine.org
>_______________________________________________
>nginx mailing list
>nginx at nginx.org
>http://mailman.nginx.org/mailman/listinfo/nginx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20181208/d94db443/attachment.html>