On Mon, Mar 30, 2015 at 8:46 PM, Jonathan Matthews <[email protected]> wrote: > On 30 Mar 2015 18:59, "Kevin Day" <[email protected]> wrote: >> >> I have a use case where I need to be able to take an incoming request like >> "/XXX/filename" and translate that to fetching >> "http://nodeXXX.example.com/filename"; where there'd literally be hundreds of >> backend servers. i.e. XXX would be a varying 3 digit number. >> >> I saw this post here: >> >> >> https://www.varnish-software.com/blog/truly-dynamic-backend-definition-varnish >> >> From 2012, but I know a lot has changed since then. Is there an easy way >> this can be accomplished now? > > Modulo a significant advance in varnish dynamic backends I've missed, I'd do > this with Varnish talking to one or more local or remote Nginx instances - > it's trivial to implement that dynamic routing there. I wouldn't move to > nginx alone however - varnish definitely does a better job of caching. IMHO > & IME :-)
Hi, Forget about nginx, you could easily do this with HAProxy. It requires a bit of rewriting then either a map or use-server rule with the freshly created Host header :) And it is processed at light speed without any latency. Baptiste _______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
