-
-
Notifications
You must be signed in to change notification settings - Fork 189
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
BUGFIX: Wrong port assigned in applyTo() #2654
BUGFIX: Wrong port assigned in applyTo() #2654
Conversation
This fixes the following: - given an HTTPS connection to a proxy that passes the request handling to a server via HTTP - given a shortcut node pointing to `http://www.acme.com` - will result in `http://www.acme.com:443` leading to errors This fixes it by using the (at this point already set!) scheme of the `$uri` to fill in the standard port.
Let's see if any test fails now… 😎 |
Ok, question… How on earth does that expectation make any sense?
I mean, if I really want to talk HTTPS to port 80, I better pass in the port explicitly. No? |
For me that second dataset should be [
'constraints' => [UriConstraints::CONSTRAINT_SCHEME => 'https'],
'templateUri' => 'http://some-domain.tld',
'forceAbsoluteUri' => false,
'expectedUri' => 'https://some-domain.tld/'
] or (in case we really want the "weird combo") [
'constraints' => [UriConstraints::CONSTRAINT_SCHEME => 'https', UriConstraints::CONSTRAINT_PORT => 80],
'templateUri' => 'http://some-domain.tld',
'forceAbsoluteUri' => false,
'expectedUri' => 'https://some-domain.tld/'
] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, somehow makes sense...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that makes a lot of sense. Thanks for taking care!
This fixes the following:
http://www.acme.com
http://www.acme.com:443
leading to errorsThis fixes it by using the (at this point already set!) scheme of the
$uri
to fill in the standardport.