You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2020/10/06 09:45:17 UTC

[GitHub] [apisix] spacewander commented on issue #1226: feature: Support follow redirect

spacewander commented on issue #1226:
URL: https://github.com/apache/apisix/issues/1226#issuecomment-704156541


   IMHO, I don't like this idea because it doesn't obey the HTTP "convention". Clients like curl can follow redirect because they are clients, but let the proxy follow the redirect looks bad to me. Is there a strong reason to add this feature?
   
   Considering client request a domain A with A's cookie, and A redirects the Client to domain B.
   When client requests to domain B, it will take the B's cookie with it.
   
   If we consume the redirect, there is no way for us to know the domain B's cookie and create a request with the cookie attached.
   
   There will be some trouble with cache and TLS too, maybe something else which haven't come to my mind yet.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org