New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[gateway] Host header sent to HTTPS backend API is not accurate #427

Closed
brasseld opened this Issue Jan 26, 2017 · 0 comments

Comments

Projects
None yet
2 participants
@brasseld
Member

brasseld commented Jan 26, 2017

Host HTTP header does not have to contain port in case of HTTP or HTTPS protocol for 80 or 443.
Unfortunately, some proxy or HTTP server does not support host value with port (443) in case of HTTPS.
So, we need to remove the port for both HTTP (80) and HTTPS (443) from Host header.

@brasseld brasseld added this to the 1.3.0 milestone Jan 26, 2017

@brasseld brasseld self-assigned this Jan 26, 2017

@brasseld brasseld changed the title from [gateway] Host header sent to the backend API to [gateway] Host header sent to HTTPS backend API is not accurate Jan 26, 2017

brasseld added a commit to gravitee-io/gravitee-gateway that referenced this issue Jan 26, 2017

NicolasGeraud added a commit to gravitee-io/gravitee-gateway that referenced this issue Jan 27, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment