Incompleted (truncated) PHP output
proforg at maloletka.ru
Tue Jul 3 04:39:53 MSD 2007
On 02.07.2007, at 22:10, Huan Truong wrote:
> Hi all,
> I met a very weird problem with nginx and PHP - nginx - in some
> very rare cases, does not return the whole content of php script.
> For example, this page:
> - isn't returned correctly -- It is truncated. Some other files are
> also truncated, and that files resulted uncompleted web pages.
> One more example: http://hpvn.net/forum/showthread.php?t=47x
> Seems that nginx doesn't like php scripts that produce too long
No, it looks like backend<-->frontend communication problems
(missunderstanding :). Is it possible to have nginx debug log for
such a request ?
> I have checked all the configurations in php.ini and nginx.conf but
> couldn't find anything wrong - I have updated nginx to the lastest
> but both .56 and .61 have the same problem.
Actually it looks like problem is gzip compression prodused by php,
which is not correctly handled by nginx. Likely the same problem was
discussed in russian nginx mail list two days ago. As a quick
workaround (at least while Igor is on vacation) try to disbale gzip
encoding and usage of cached gzipped files on backend by replacing
tiny_mce_gzip.php with tiny_mce.php. And generally it's better not to
rely on php gzip/deflate handlers at all - use nginx mod_gzip
> This is my phpinfo file: http://tnhh.info/phpinfo.php
> Anyone has experienced this? Please help me.
> Thanks in advance.
> Huan, Truong -- huantnh at gmail.com
> Visit my personal homepage: http://tnhh.info/
Email/JID: proforg at maloletka.ru
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 2423 bytes
Desc: not available
More information about the nginx