Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[HttpClient] Disable HTTP/2 PUSH by default when using curl #57870

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

Merged
merged 1 commit into from
Jul 29, 2024

Conversation

nicolas-grekas
Copy link
Member

Q A
Branch? 5.4
Bug fix? yes
New feature? no
Deprecations? no
Issues Fix #57681
License MIT

I propose to disable HTTP/2 PUSH by default when using curl. Amp still supports it out of the box, but support in curl is too fragile (it segfaults, see linked issue).

We have to balance:

  • seeing a perf downgrade for apps that might benefit from pushes
  • vs putting every users at risk with a possible segfault when a server sends PUSH frames

Preventing this possible segfault is the most important here IMHO. Apps that leverage PUSH should be rare, and can re-enable if they really want to.

Copy link
Member

@chalasr chalasr left a comment

Choose a reason for hiding this comment

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

👍 for disabling push by default (https://developer.chrome.com/blog/removing-push). No strong opinion about targeting 5.4 vs 7.2 but if it's broken then fine merging this as a bugfix.

@nicolas-grekas nicolas-grekas merged commit a787ab9 into symfony:5.4 Jul 29, 2024
10 of 12 checks passed
@nicolas-grekas nicolas-grekas deleted the hc-no-push branch July 29, 2024 18:52
This was referenced Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants