It can, you will have to play a bit with the retry/restart mechanics after changing and cleaning bereq.url.
On Dec 1, 2016 23:49, "Star Dot" <[email protected]> wrote: > Hello! > > I am dealing with Varnish 4 piping requests to a backend server. The > backend server processes the request and redirects to Amazon S3 to serve > the actual file. > > So in short : > > Request -> Varnish -> Nginx 302 Redirect -> Amazon S3 file > > Varnish is happily caching the 302 response only, but I'm curious if I can > somehow follow the redirect and cache the destination file completely? This > will alleviate load off the nginx server obviously. > > I've seen several topics dance around this issue but I'm curious if > osmeone can point me in the right direction! > > Thanks > -- > > > StackStar Managed Hosting Services : https://www.stackstar.com > Shift8 Web Design in Toronto : https://www.shift8web.ca > > _______________________________________________ > varnish-misc mailing list > [email protected] > https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc >
_______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
