Opened 5 years ago
Closed 18 months ago
#1935 closed enhancement (wontfix)
Send cookie headers with HTTP2 Server Push
| Reported by: | https://stackoverflow.com/users/769308/jaap3 | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | nginx-module | Version: | 1.17.x |
| Keywords: | http2 server push cookies | Cc: | |
| uname -a: | |||
| nginx -V: | nginx version: nginx/1.16.1 | ||
Description
I was experimenting with the use of HTTP2 Server Push to accelerate redirects by adding a Link: <location>; as=document; rel=preload to redirect responses.
I had some success, but noticed unwanted behavior on redirects to resources that require specific cookies (e.g. a session identifier).
It turns out that nginx doesn't forward the cookie header to the resource that's being pushed.
It seems that this is by design. I came across issue #1817 and #1851 and assume that this ticket will be closed as a duplicate.
I wonder if there is some spec text I can refer to that rules out these headers.
Note:
See TracTickets
for help on using tickets.
As per #2432, HTTP/2 server push support has been removed in nginx 1.25.1, and therefore this enhancement is no longer relevant.