i am seeing many error log messages relating to SPDY on an HTTPS only
website here. this appears to also be triggering (or at least related
database timing problems, which is causing dbase failures.
the error log contains mostly these:
“inflate() failed: -5 while processing SPDY”
anyone know what’s occuring here? i think i already asked a similar
on a forum and someone pointed to the possibility of there being
exploits made against SSL3 / openSSL - though i have no direct evidence
thanks, looks like the same error message is buried in that change /
yes - though i am no closer to discerning the original cause of the
being triggered, since i am not familiar with the nginx sourecode at
any tips are welcomed!
thanks, looks like the same error message is buried in that change / code,
yes - though i am no closer to discerning the original cause of the error
being triggered, since i am not familiar with the nginx sourecode at this
any tips are welcomed!
There’s no way to find out what caused the error only by looking to
error message. You should provide the debug log at least.
enabling debug on the site in question generated vast amounts of log
and i think either some type of limit was reached or a bug caused the
logging to fail. i was unable to open the logviewer for the site’s error
after the first few minutes and eventually the interface crashed while
attempting to open the log.
now i have disabled debug again and can open the log. the logging
shortly after i initialised the debug directive for nginx, so there is
useful debug info pertaining to the SPDY issues yet.
i’m not entirely sure what to do here…
has anyone seen this type of behavior before?
i was having a lot of trouble with 302 errors initially and then later
was having slow TLS performance… i had difficulty finding the right
combination of buffer settings to get the site to run reliably and
if i recall correctly, that was a field that i changed while i was in
process of stabilising the site. possibly there was no need to change
one and i just left the change in the file once the site stabilised.
the lines in the current config are:
large_client_header_buffers 2 1k;
i don’t truly know how to set the values for these perfectly.
do you recommend to remove ‘large_client_header_buffers’ completely? or