Frank Bille-Stauner
Frank Bille-Stauner
There are two tests that fail as a consequence of the change to `PathProcessor`, because they expect there to be parameters on top level. When [PathProcessor.addParametersToEachOperation](https://github.com/swagger-api/swagger-parser/blob/3f89a9a624394537098d07b6a1c1f676e747ad9e/modules/swagger-parser-v3/src/main/java/io/swagger/v3/parser/processors/PathsProcessor.java#L93) is called it ends...
It was actually because of traefik I found this. The latest traefik version sets X-Forwarded-For to an IP address, and X-Forwarded-Host to the original requested hostname. I understand the point...
I am fairly new to Traefik, but I think they have been using [Oxy](https://github.com/vulcand/oxy) for a long time (It is the library handling the proxying). And Oxy has been using...
That is quite odd. Have you checked that the X-Forwarded-For header is set? And it is an actual hostname and not an IP? I'm also reading up on this now...
But that passes the "Host" header, and according to the [resolveHost](https://github.com/gin-contrib/location/blob/master/config.go#L60) algorithm it will never get to that if the X-Forwarded-For header is set. The algorithm is: 1) X-Forwarded-For header...