Skip to content

Conversation

remicollet
Copy link
Member

No description provided.

@remicollet
Copy link
Member Author

@remicollet
Copy link
Member Author

@krakjoe open as PR as I'd like to get @sgolemon feeling.

If accepted, will have to be cherry-picked in 7.1.4 before release.

@remicollet
Copy link
Member Author

I just change from > 1 to > 2 to avoid using empty string (BTW proxy="/" is obviously wrong)

@remicollet remicollet changed the base branch from master to PHP-7.1 March 30, 2017 08:01
@krakjoe
Copy link
Member

krakjoe commented Mar 30, 2017

ack, awaiting Sara

@remicollet remicollet changed the base branch from PHP-7.1 to PHP-7.0 March 30, 2017 09:37
@remicollet remicollet changed the base branch from PHP-7.0 to PHP-7.1 March 30, 2017 09:38
@remicollet
Copy link
Member Author

As http://git.php.net/?p=php-src.git;a=commitdiff;h=bab0b99f376dac9170ac81382a5ed526938d595a was applied in 7.0, also needed in 7.0.18 /cc @weltling

@weltling
Copy link
Contributor

@remicollet yeah, it is in there, thanks for the ping.

IMO we should not touch this. We'd otherwise would have to fix any special cases where any other garbage is appended to the port number, etc. AFM, the BC impact is acceptable in this case, as there's a low security impact and the test data is broken itself.

Otherwise, probably a fix to this should be generalized, not checking for an explicit char like '/' at the end, but cutting off the non numeric garbage. Frankly, i'd not see it worth the effort as it might get complicated.

Thanks.

@sgolemon
Copy link
Member

sgolemon commented Apr 3, 2017

Ergh.... um.... I don't think we should preserve BC for transport strings that are broken by design. I regard this as a bug in Guzzle's test. The fact that garbage used to be ignored isn't an endorsement for allowing garbage indefinitely.

@sgolemon
Copy link
Member

sgolemon commented Apr 3, 2017

At the absolute very least, garbage should be cause for raising a warning, so if we do need to pull something like this onto 7.0 and 7.1*, then it should make it clear that those transport strings are malformed.

  • The BC argument goes away for 7.2 IMO, since 7.2.0 isn't out yet.

@remicollet
Copy link
Member Author

I think we have consensus on keeping as it is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants