Skip to main content

#Firefox joins the other browsers and disables HTTP/2 server push.

libcurl still supports it!

groups.google.com/a/mozilla.or…

#firefox
in reply to daniel:// stenberg://

Stefan Eissing
Stefan Eissing
• •
Now a *very* niche feature. We probably do not know enough of its use in libcurl to rip it out as well?
in reply to daniel:// stenberg://

Adam Piggott
Adam Piggott
• •
"unship" is some microspeak-grade vernacular. They could have at least used "sink" or "scuttle".
in reply to daniel:// stenberg://

Cory Benfield
Cory Benfield
• •
I'm honestly amazed I haven't had the courage just to default that setting to off. It only surprises users.
in reply to Cory Benfield

daniel:// stenberg://
daniel:// stenberg://
• •
@lukasa in curl's case we only offer it via an API but that also means we cannot very easily take it away without risking hurting a few users... Ie we would need to bump SONAME.
@Cory Benfield
in reply to daniel:// stenberg://

Cory Benfield
Cory Benfield
• •
Oh sure, the same is true for Swift. The thing that I haven't done yet is change our default settings. Currently we leave SETTINGS_ENABLE_PUSH at their defaults, so "on" for clients. I'm wondering about just switching it off unilaterally.
⇧