Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Protocol is applied to load balancing upstream target #3259
Comments
|
I have investigated this on the latest master. I followed the mentioned steps and failed to reproduce it. I remember when this was first opened I was able to reproduce it, it seems someone pushed unrelated changes that addressed this issue. I'm closing this for now, if you can still reproduce this on latest mater branch you can reopen it with new info on how to reproduce it. |
Fixes #3259 This refactors EnsureTransport function for properly ensuring transport is present on the host when load balancer is enabled. We rely on url.Parse to do heavy lifting. We add missing Scheme field to make sure URL.String will return a valid upstream host.
* Fix ensuring transport to upstream Fixes #3259 This refactors EnsureTransport function for properly ensuring transport is present on the host when load balancer is enabled. We rely on url.Parse to do heavy lifting. We add missing Scheme field to make sure URL.String will return a valid upstream host. * use http when scheme and protocol are missing
* Fix ensuring transport to upstream Fixes #3259 This refactors EnsureTransport function for properly ensuring transport is present on the host when load balancer is enabled. We rely on url.Parse to do heavy lifting. We add missing Scheme field to make sure URL.String will return a valid upstream host. * use http when scheme and protocol are missing (cherry picked from commit 3434dc8)
* Fix ensuring transport to upstream Fixes #3259 This refactors EnsureTransport function for properly ensuring transport is present on the host when load balancer is enabled. We rely on url.Parse to do heavy lifting. We add missing Scheme field to make sure URL.String will return a valid upstream host. * use http when scheme and protocol are missing (cherry picked from commit 3434dc8)

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

Branch/Environment/Version
Describe the bug
When we set protocol on api definition and enable load balancing, protocol is applied on upstream targets.
Reproduction steps
Actual behavior
Gateway will return 500 error since upstream target is
https://http://httpbin.org/Expected behavior
Gateway should ignore protocol during proxying
Screenshots/Video
If applicable, add screenshots or video to help explain your problem.
Logs (debug mode or log file):
Configuration (tyk config file):
Attach tyk configuration file
Additional context
Testing api definition