May be it's important, before i added *SetEnv no-gzip 1* , i saw in apache 
logs that request is reaching the server, and response is sent back with no 
errors.
some users was even able to see correct response, but some got *curl_error 
= Error while processing content unencoding: invalid block type *
or ERR_CONTENT_DECODING_FAILED.

so i dig for that problem, and found out about gzip issue.


четверг, 25 августа 2016 г., 11:37:33 UTC+6 пользователь Anatoly Piskunov 
написал:
>
> Hello again!
>
> i've faced with another related problem, and rely on your competent help 
> only!
>
> recently, i've been posting my app. And when somebody calls my url, gets 
> "ERR_CONTENT_DECODING_FAILED" or curl_err:23
> so i added SetEnv no-gzip 1 into my VirtualHost Directory.
> it now looks like:
>         <Directory /home/user01/nano_fb_py_bot/nano_fb_py_bot>
>         SetEnv no-gzip 1
>         <Files wsgi.py>
>         Require all granted
>         </Files>
>         </Directory>
> funny thing is, when now somebody requests url, he gets
>
>
> *%valid_response_string%*<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 
> 2.0//EN">
> <html><head>
> <title>500 Internal Server Error</title>
> </head><body>
> <h1>Internal Server Error</h1>
> <p>The server encountered an internal error or
> misconfiguration and was unable to complete
> your request.</p>
> <p>Please contact the server administrator at 
> webmaster@localhost to inform them of the time this error occurred,
> and the actions you performed just before this error.</p>
> <p>More information about this error may be available
> in the server error log.</p>
> <hr>
> <address>Apache/2.4.7 (Ubuntu) Server at kcl16bt08.kcell.kz Port 443
> </address>
> </body></html>
>
> in the apache log i see the same *Truncated or oversized response headers 
> received from daemon process*
>
> any ideas on that Graham?
>

-- 
You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.

Reply via email to