if the upstream responds with a redirect, typically it will send an absolute path that will not match the one Kong clients are calling _(both request host and request path)_.
a follow_redirects directive on the API would instruct nginx to retry the same request at the new location before sending back to the client, thus eliminating the need for the client to know about the redirect.
ahmadnassri
All 10 comments
Should probably use proxy_redirect.
thibaultcha
on 6 Jan 2016
Proxy_redirect would fix the issue nicely :)
catchdave
on 8 Jan 2016
+1, this would be particularly useful when the redirect from the upstream host is unreachable from the end user's machine, but is reachable by Kong (e.g. Kong is exposing an internal service).
3dbrows
on 28 Jan 2016
+1
anamarialazar
on 5 Apr 2016
+1 Need this too
JnMik
on 6 Mar 2017
+1 also need this
lnryan
on 9 May 2017
+1 same here
kl4n4
on 1 Jun 2017
+1 need this too
john-deng
on 23 Jul 2017
+1 looking for this
jakebolam
on 5 Mar 2018
+1 this would be a much-needed option in kong itself (instead of fiddling with the underlying nginx configs)
MingStar
on 24 Oct 2018
Related issues
kwahome
路
3Comments
Voronenko
路
3Comments
cospotato
路
3Comments
vikaskmr1008
路
3Comments
gopirajum
路
3Comments
Most helpful comment
+1, this would be particularly useful when the redirect from the upstream host is unreachable from the end user's machine, but is reachable by Kong (e.g. Kong is exposing an internal service).