But if you include a variable in proxy_pass, nginx resolves http://example.com on demand and caches it per the DNS record's TTL:
location / {
resolver 127.0.0.1;
set $empty "";
proxy_pass http://example.com $empty;
}
(2/2)
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I remember this bit me once, make sure you set the timeouts explicitly otherwise things don’t pay attention to resolver and just gets cached forever
-
Documentation says it respects the TTL, no need to explicitly set any timeouts. My testing on nginx 1.6.2 confirms this.
-
Cool, this happened 2yrs ago probably fixed now
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.