Skip to content
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

[RFR] fix scheme problem whith reverse proxy #1128

Closed
wants to merge 1 commit into from
Closed

[RFR] fix scheme problem whith reverse proxy #1128

wants to merge 1 commit into from

Conversation

zoneprog
Copy link

Q A
Branch? 2.0
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets 727
License MIT
Doc PR

Solution if you're behind a reverse proxy handling the HTTPS stuff and dispatching the requests as HTTP to various Docker containers running the actual Symfony application.

@daFish
Copy link
Contributor

daFish commented Nov 26, 2018

This looks like a fix which is also covered (in a different way) by #1059.

@maximgubar
Copy link
Contributor

Hi @zoneprog ,
Thank you for the merge request,
could you please merge latest master in your branch in order to pass the CI ?

Copy link
Member

@dbu dbu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i have some vague memory about symfony providing information correctly when you configure it correctly to trust the reverse proxy. could that be the problem, or should we look at other information?

$this->requestContext->getHost(),
$port,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this will break if a site runs on a non-default port. i think we do need to keep the port handling.

@dbu
Copy link
Member

dbu commented Aug 22, 2019

@dbu dbu closed this Aug 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants