Opened 2 years ago
Closed 18 months ago
#2432 closed enhancement (fixed)
deprecate HTTP/2 Server Push and port to 103 Early Hints
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | nginx-core | Version: | 1.23.x |
Keywords: | Cc: | adrelanos@… | |
uname -a: | |||
nginx -V: | 1.23.x |
Description
HTTP/2 Server Push (the link:
HTTP header) has been deprecated:
developer.chrome.com/blog/removing-push/
It is being replaced by 103 Early Hints:
developer.chrome.com/blog/early-hints/
developer.mozilla.org/en-US/docs/Web/HTTP/Status/103
Change History (3)
comment:1 by , 2 years ago
Priority: | major → minor |
---|---|
Type: | defect → enhancement |
comment:3 by , 18 months ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
HTTP/2 server push support has been removed in nginx 1.25.1. Recommended replacement, if at all, is to use Link: rel=preload
HTTP header.
Closing this. Thanks to all involved.
Note:
See TracTickets
for help on using tickets.
I do agree that HTTP/2 Server Push support needs to be removed. It is mostly equivalent to "Link: rel=preload" HTTP header, and adds little to no value (or even negative value, as per Chrome study).
Note though that implementing
103 Early Hints
is a separate thing. Further, it will require some major work to be done, as currently nginx has no infrastructure to handle 1xx informational responses.