Upcoming SPDY support details

Alek Storm alek.storm at gmail.com
Thu May 17 12:06:21 UTC 2012

On Thu, May 17, 2012 at 6:23 AM, Valentin V. Bartenev <ne at vbart.ru> wrote:

> First implementation of SPDY support will work only on frontend side. So,
> nginx
> will be able to talk with backends by HTTP, FastCGI, uwsgi, or SCGI
> protocols.

Got it. Looking forward to backend SPDY support, so crucial advantages like
multiplexing are preserved. Will nginx at least add headers like
"X-Priority" to the forwarded request?

First implementation will have no support of SPDY server push. I believe
> that
> the next step is to add pushing by special response header from backend
> (like
> "X-Accel-Redirect" but with the list of URIs to push).

That'll work, but am I correct in assuming that the response containing
"X-Accel-Redirect" is different from the response to the original request?
If they are the same, then nginx will not be notified of the URIs to push
until the server is ready to send the headers for the response to the
original request. This would be more restrictive than SPDY's semantics,
which allow pushing resources before the SYN_REPLY frame for the original
request is even sent.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx-devel/attachments/20120517/ac64d61d/attachment.html>

More information about the nginx-devel mailing list