nginx 1.5.10 now supports SPDY 3.1

for those running SPDY on a Centminmod install, did you have any issues initially with CSS not displaying correctly on Chrome but working on other browsers? tracking down a bizarre issue after enabling SSL/TLS+SPDY where CSS just wont render at all in Chrome.
No probs with Centmin Mod and SPDY and ngx_pagespeed on my installations either.
 
Not using centminmod, but not sure why that would cause CSS to fail...
zeroing in on some issues with the way php-fpm is installed with SSL support i think, causing odd 304s and other stuff to be punted to Chrome. still have more testing to do.
 
Changes with nginx 1.5.11 04 Mar 2014

*) Security: memory corruption might occur in a worker process on 32-bit
platforms while handling a specially crafted request by
ngx_http_spdy_module, potentially resulting in arbitrary code
execution (CVE-2014-0088); the bug had appeared in 1.5.10.
Thanks to Lucas Molas, researcher at Programa STIC, Fundación Dr.
Manuel Sadosky, Buenos Aires, Argentina.

*) Feature: the $ssl_session_reused variable.

*) Bugfix: the "client_max_body_size" directive might not work when
reading a request body using chunked transfer encoding; the bug had
appeared in 1.3.9.
Thanks to Lucas Molas.

*) Bugfix: a segmentation fault might occur in a worker process when
proxying WebSocket connections.

*) Bugfix: a segmentation fault might occur in a worker process if the
ngx_http_spdy_module was used on 32-bit platforms; the bug had
appeared in 1.5.10.

*) Bugfix: the $upstream_status variable might contain wrong data if the
"proxy_cache_use_stale" or "proxy_cache_revalidate" directives were
used.
Thanks to Piotr Sikora.

*) Bugfix: a segmentation fault might occur in a worker process if
errors with code 400 were redirected to a named location using the
"error_page" directive.

*) Bugfix: nginx/Windows could not be built with Visual Studio 2013.
 
1.7 builds OK with Centminmod

Code:
[root@test centmin-v1.2.3mod]# nginx -v
nginx version: nginx/1.7.0
 
Top Bottom