Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#1409 closed defect (invalid)

ERR_SPDY_PROTOCOL_ERROR

Reported by: linuxhpceng@… Owned by:
Priority: major Milestone:
Component: other Version: 1.12.x
Keywords: Cc:
uname -a: 3.10.0-327.el7.x86_64 #1 SMP Thu Oct 29 17:29:29 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux
nginx -V: nginx version: nginx/1.12.2
built by gcc 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC)
built with OpenSSL 1.0.2k-fips 26 Jan 2017
TLS SNI support enabled
configure arguments: --prefix=/etc/nginx --sbin-path=/usr/sbin/nginx --modules-path=/usr/lib64/nginx/modules --conf-path=/etc/nginx/nginx.conf --error-log-path=/var/log/nginx/error.log --http-log-path=/var/log/nginx/access.log --pid-path=/var/run/nginx.pid --lock-path=/var/run/nginx.lock --http-client-body-temp-path=/var/cache/nginx/client_temp --http-proxy-temp-path=/var/cache/nginx/proxy_temp --http-fastcgi-temp-path=/var/cache/nginx/fastcgi_temp --http-uwsgi-temp-path=/var/cache/nginx/uwsgi_temp --http-scgi-temp-path=/var/cache/nginx/scgi_temp --user=nginx --group=nginx --with-compat --with-file-aio --with-threads --with-http_addition_module --with-http_auth_request_module --with-http_dav_module --with-http_flv_module --with-http_gunzip_module --with-http_gzip_static_module --with-http_mp4_module --with-http_random_index_module --with-http_realip_module --with-http_secure_link_module --with-http_slice_module --with-http_ssl_module --with-http_stub_status_module --with-http_sub_module --with-http_v2_module --with-mail --with-mail_ssl_module --with-stream --with-stream_realip_module --with-stream_ssl_module --with-stream_ssl_preread_module --with-cc-opt='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -fPIC' --with-ld-opt='-Wl,-z,relro -Wl,-z,now -pie'

Description

This site can’t be reached

The webpage at https://somewebsite.com/ might be temporarily down or it may have moved permanently to a new web address.
ERR_SPDY_PROTOCOL_ERROR

Any time add_header Cache-Control of any kind is inserted into the config. The site breaks with a SPDY error. It does not matter if httpd2 is on or off. It fails the same either way.

Attachments (1)

nginxconfig.conf (2.4 KB ) - added by linuxhpceng@… 3 years ago.
Actual config.

Download all attachments as: .zip

Change History (7)

by linuxhpceng@…, 3 years ago

Attachment: nginxconfig.conf added

Actual config.

in reply to:  description comment:1 by linuxhpceng@…, 3 years ago

It might be worth noting that it works in FireFox but not chrome or I.E.

Replying to linuxhpceng@…:

This site can’t be reached

The webpage at https://somewebsite.com/ might be temporarily down or it may have moved permanently to a new web address.
ERR_SPDY_PROTOCOL_ERROR

Any time add_header Cache-Control of any kind is inserted into the config. The site breaks with a SPDY error. It does not matter if httpd2 is on or off. It fails the same either way.

comment:2 by Valentin V. Bartenev, 3 years ago

Resolution: invalid
Status: newclosed

In your configuration, instead of Cache-Control you try to add Cache-Control: (with a surplus colon at the end).

Here's how it should look like:

add_header Cache-Control max-age=2592000;

Here's what you have:

add_header Cache-Control: max-age=2592000;

comment:3 by linuxhpceng@…, 3 years ago

Thank you for the reply.

I must have removed that : when I was scrubbing the config.

# add_header Cache-Control: max-age=2592000;
# add_header Cache-Control: public;
# add_header Cache-Control: "public, max-age=604800";

The ones above are the 3 that exist in the config. Doesn't matter which one of those I use it always has the same problem.

comment:4 by linuxhpceng@…, 3 years ago

Why would you close the ticket? This is clearly a problem that needs to be resolved. The colon exists as it should in the non-working configuration.

comment:5 by linuxhpceng@…, 3 years ago

I read your comment exactly backwards.

I made the changes and things started working.. This is bizarre because it used to work.

Either way.

Thank you for your time.

in reply to:  5 comment:6 by kris.spam.kauper.net@…, 3 years ago

Replying to linuxhpceng@…:

I read your comment exactly backwards.

I made the changes and things started working.. This is bizarre because it used to work.

Either way.

Thank you for your time.

Did you update the configuration for the somewebsite.com server? I still get the same SPDY error for that site.

Note: See TracTickets for help on using tickets.