#Firefox joins the other browsers and disables HTTP/2 server push.
libcurl still supports it!
https://groups.google.com/a/mozilla.org/g/dev-platform/c/vU9hJg343U8/m/4cZsHz7TAQAJ?pli=1
HTTP/1.1 was such a lovely protocol.
@[email protected] WHYYYYY. Curse Chrome just deleting things for no reason
@[email protected] I’m honestly amazed I haven’t had the courage just to default that setting to off. It only surprises users.
@[email protected] 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.
@[email protected] 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.
@[email protected] “unship” is some microspeak-grade vernacular. They could have at least used “sink” or “scuttle”.
@[email protected] Now a very niche feature. We probably do not know enough of its use in libcurl to rip it out as well?
@[email protected] right, presumably not widely used but we can’t really tell…
