Zuul add-proxy-headers could be aware of upstream X-Forwarded-* headers

[kakawait]

It may possible the following problem is not an issue

Using following architecture

                +      ^
                |      |
                |      |
                v      +
            +-------------+
            |  Reverse    |
            |  Proxy SSL  |
            +-------------+
                +      ^
                |      |
                |      |
                v      +
            +-------------+
            |             |
            |     ZUUL    |
            +-------------+
                ^   ^   ^
         +------+   |   +-----+
         |          |         |
         v          v         v
      +------+   +------+  +------+
      |      |   |      |  |      |
      | m1   |   | m2   |  | m3   |
      |      |   |      |  |      |
      +------+   +------+  +------+

Where Reverse proxy SSL could be Nginx/Apache thus Zuul and all microservices communications is under HTTP.

Basically Reverse proxy SSL add X-Forwarded-* headers on downstream like:

• X-Forwarded-Host
• X-Forwarded-Proto
• X-Forwarded-Port
• X-Forwarded-Prefix for context path

But when using properties zuul.add-proxy-headers to true Zuul does not care about these headers and my hostname will be transformed to localhost

In other hand if zuul.add-proxy-headers to false headers are correctly transmitted by X-Forwarded-Prefix becomes not reliable. Indeed X-Forwarded-Prefix will not be updated to correct context-path of the given microservices/routes.

May I miss something? Possible solution is to set zuul.add-proxy-headers to false and write my own ZuulFilter. If you think is not common case feel free to close issue. Could be dup of #352

[kakawait]

Never mind issue come from stripPrefix: false. I will close it for now.