# Fwd: Announcing SPDY draft 2 implementation in nginx

**URL:** <https://www.ruby-forum.com/t/fwd-announcing-spdy-draft-2-implementation-in-nginx/220658>\
**Category:** NGINX\
**Created:** [June 15, 2012, 2:46pm UTC](https://www.ruby-forum.com/t/fwd-announcing-spdy-draft-2-implementation-in-nginx/220658 "2012-06-15T14:46:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![aris](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/258eb7/32.png) [@aris](https://www.ruby-forum.com/u/aris)\
**Post date:** [June 15, 2012, 2:46pm UTC](https://www.ruby-forum.com/t/fwd-announcing-spdy-draft-2-implementation-in-nginx/220658/1 "2012-06-15T14:46:58Z")

</div>

For those who don’t read -devel but still want to try the patch:

[http://nginx.org/patches/spdy/](http://nginx.org/patches/spdy/)

-------- Original Message --------  
Subject: Announcing SPDY draft 2 implementation in nginx  
Date: Fri, 15 Jun 2012 16:40:57 +0400  
From: Valentin V. Bartenev [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
Reply-To: removed\_email\_address@domain.invalid  
To: removed\_email\_address@domain.invalid

We are pleased to announce the first beta version of SPDY draft 2  
module for nginx.

It is currently distributed as a patch for nginx 1.3.x development  
version.

For more information about SPDY protocol specification please check  
[http://www.chromium.org/spdy/spdy-protocol](http://www.chromium.org/spdy/spdy-protocol)

Known problems and limitations of this revision:

- server push is not supported;

- post\_action directive is not supported for SPDY connections;

- rate limiting is not supported for SPDY connections;

- SSL buffer is switched off.

We will be working on improving SPDY support during the next few  
months with the goal of eventually integrating it fully into the  
main nginx code. Expect frequent updates about this development,  
and please report your experiences, and send the feedback to nginx  
development mailing list removed\_email\_address@domain.invalid (check  
[nginx-devel Info Page](http://mailman.nginx.org/mailman/listinfo/nginx-devel)).

Configuration and installation instructions are below.

How to build nginx/spdy binary:

1. Install OpenSSL 1.0.1, it’s required because SPDY module uses  
Next Protocol Negotiation TLS extension.

2. Download nginx 1.3.x tar-gzip package (check  
[nginx: download](http://nginx.org/en/download.html))

3. Unpack nginx-1.3

4. Download and apply SPDY module patch

5. Configure nginx build

6. Build nginx

To enable SPDY in nginx configuration, just add “spdy” and “ssl”  
parameters to the listen directive:

server {  
listen 443 ssl spdy default\_server;

```
  ssl_certificate server.crt;
  ssl_certificate_key server.key;

  ...

```

}

Optional SPDY configuration directives:

- spdy\_recv\_buffer\_size - specifies the size of input buffer (per  
worker), 1MB by default;

- spdy\_max\_concurrent\_streams - maximum number of concurrent SPDY  
streams in a single connection, 100 by default;

- spdy\_streams\_index\_size - size of SPDY stream ID index, should  
be power of 2, default is 32;

- spdy\_recv\_timeout - timeout when expecting more data from the  
client, default is 30s;

- spdy\_keepalive\_timeout - inactivity timeout after which connection  
is closed, default is 3m;

- spdy\_headers\_comp - header compression level (0 = no comp, 9 =  
max comp), default is 1;

- spdy\_headers\_comp\_window - size of LZ77 compression window,  
default is 4KB.

The default values are more or less optimized for generic use,  
there’s normally no need to tweak them.

SPDY variables:

- $spdy - version of SPDY protocol if the request came via SPDY  
(currently “2”), or empty value;

- $spdy\_request\_priority - priority of the stream, if the request  
came via SPDY.

Disclaimer: use this code at your own risk, it is distributed under  
the 2-clause BSD-like license, and at nginx we are not responsible  
for any negative impact or effects that the usage of this code might  
cause.

–  
NGINX, Inc., [http://nginx.com](http://nginx.com)

* * *

nginx-devel mailing list  
removed\_email\_address@domain.invalid  
[http://mailman.nginx.org/mailman/listinfo/nginx-devel](http://mailman.nginx.org/mailman/listinfo/nginx-devel)

–  
Maxim K.  
+7 (910) 4293178

> **[Advanced Load Balancer, Web Server, & Reverse Proxy - NGINX](https://www.nginx.com/)**
>
> NGINX accelerates content and application delivery, improves security, and facilitates availability and scalability for the busiest websites on the Internet.

---

<div class="post-metadata">

**Author:** ![xamdam](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/x/d78d45/32.png) [@xamdam](https://www.ruby-forum.com/u/xamdam)\
**Post date:** [June 15, 2012, 3:40pm UTC](https://www.ruby-forum.com/t/fwd-announcing-spdy-draft-2-implementation-in-nginx/220658/2 "2012-06-15T15:40:45Z")

</div>

Thanks for your job.

by the way why not push this mail to spdy maillist?