HTTP/405

https://tools.ietf.org/html/rfc7231#page-59 says: ... The origin server MUST generate an Allow header field in a 405 response containing a list of the target resource's currently supported methods. nginx doesn't seem to have Allow header field. Is that against RFC? curl -v -X TRACE http://

Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!

I've noticed that its related to the orders of virtual host files. For example if vhost of mydomain.com comes first than yourdomain.com then SSL CN (common name) for both domains will be *.mydomain.com. And if vhost of yourdomain.com comes before than mydomain.com then common name for both domains

Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!

Update: Now i removed vhost for mydomain.com and yourdomain.com is now showing correct Common name. So there's some kind of overlapping in vhosts. Virus-free. www.avast.com

Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!

Hi, >>As far as I know, there are about half a dozen "latest" versions of Google Chrome, and none of them are version 64 currently. Your're right sorry, the version latest is 60. >>You have one client that reports an error message.What are the specific circumstances under which that version of

Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!

On Wed, Aug 02, 2017 at 01:17:06PM +0500, shahzaib mushtaq wrote: Hi there, > Thanks for response well i've tried lot more things, updated FreeBsd, > updated openssl but issue is still there. Do you think is there any > possibility it is linked with Nginx ? You have one client that reports an er