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

"HTTPS" Boolean Header Value in Browserkit/Client #32292

Closed
solverat opened this issue Jun 30, 2019 · 6 comments
Closed

"HTTPS" Boolean Header Value in Browserkit/Client #32292

solverat opened this issue Jun 30, 2019 · 6 comments
Milestone

Comments

@solverat
Copy link

Affected file: Symfony\Component\BrowserKit\Client

Description
guzzle/psr7 1.6 has been released which does no longer support any header values except numeric or string:

https://github.com/guzzle/psr7/blob/dc784032a3f6f4e7a4b882e272b771f6fe4c37cf/src/MessageTrait.php#L189

From now on, the request object will throw an exception because of this line:

$server['HTTPS'] = 'https' == parse_url($uri, PHP_URL_SCHEME);

Error:

"Header value must be a string or numeric but boolean provided."
@nicolas-grekas
Copy link
Member

Would you mind sending a PR to fix it? Branch 3.4 I suppose.

@nicolas-grekas
Copy link
Member

Alternatively, this could be reported as a BC break on Guzzle's side, and fixed as a bug there.
Could you please open an issue on the Guzzle repo to ask them to consider?

@nicolas-grekas nicolas-grekas added this to the 3.4 milestone Jun 30, 2019
@solverat
Copy link
Author

solverat commented Jul 1, 2019

For reference: guzzle/psr7#282

@GrahamCampbell
Copy link
Contributor

guzzle/psr7 1.6 has been released which does no longer support any header values except numeric or string

I think this was a bug fix surely, in that it just wasn't enforcing it before and it was meant to?

@sagikazarmark
Copy link

For the record: this is not a BC break in terms of following PSR-7 and enforcing types documented by it.

That being said, we are going to revert the change in the 1.x release branch and reapply it in 2.x, so fixing it in Symfony would probably also make sense.

@sagikazarmark
Copy link

1.6.1 has been tagged with the reverted change.

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

No branches or pull requests

5 participants