#396 closed defect (fixed)
Chrome <--> nginx SPDY/2 misunderstanding
| Reported by: | Илья Шипицин | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.5.3 |
| Component: | nginx-core | Version: | 1.3.x |
| Keywords: | spdy | Cc: | |
| uname -a: | |||
| nginx -V: |
nginx version: nginx/1.4.1
TLS SNI support enabled configure arguments: --prefix=/etc/nginx --with-cc=egcc --conf-path=/etc/nginx/nginx.conf --sbin-path=/usr/local/sbin/nginx --pid-path=/var/run/nginx.pid --lock-path=/var/nginx/tmp/nginx.lock --http-client-body-temp-path=/var/nginx/tmp/client_body_temp --http-proxy-temp-path=/var/nginx/tmp/proxy_temp --http-fastcgi-temp-path=/var/nginx/tmp/fastcgi_temp --http-scgi-temp-path=/var/nginx/tmp/scgi_temp --http-uwsgi-temp-path=/var/nginx/tmp/uwsgi_temp --http-log-path=/var/log/nginx/access.log --error-log-path=/var/log/nginx/error.log --user=_nginx --group=_nginx --with-http_gzip_static_module --with-http_ssl_module --with-http_stub_status_module --with-ipv6 --with-pcre-jit --with-http_realip_module --with-http_sub_module --with-http_spdy_module --with-debug --add-module=../nginx-sticky-module-1.1 --add-module=../lua-nginx-module-0.8.2rc1 |
||
Description
during XMLHttpRequest empty headers may be added. According to SPDY specifications server MUST issue stream error.
however, Chrome neglects that idea and allows empty headers to pass out.
look what happens:
https://spdy2.skbkontur.ru - nginx, SPDY/2
https://spdy3.skbkontur.ru - node.js, SPDY/3
I beleive that it is bug of Chrome, however, we can nothing or little to do here, it is not possible to upgrade 25% of internet users (how many of them use Chrome ? I beleive about 25%).
Note:
See TracTickets
for help on using tickets.
https://code.google.com/p/chromium/issues/detail?id=272734 - bug also open for Chrome