XML files truncated
Axel
junk at devignon.fr
Mon May 31 14:38:50 MSD 2010
Hi Anton,
very good idea. Here what I get:
2010/05/31 12:36:52 [crit] 22005#0: *5 open() "/usr/local/nginx/fastcgi_temp/1/00/0000000001" failed (13: Permission denied) while reading upstream, client: 93.17.75.xxx, server: www.xxx.com, request: "GET /rss/restaurants/sitemap HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "www.xxx.com"
Weird ...
Thks
Axel
Le 31 mai 2010 à 12:21, Anton Yuzhaninov a écrit :
> On 31.05.2010 13:43, Axel wrote:
>> I recently migrated from Apache to Nginx. Really cool. My website is much faster. BUT I have a really weird issue that didn't occur with Apache. It seems that some big files are sometimes truncated by the server. For instance, I generate a 200 entries videos sitemap (4600 lines) for Google (Google allows up to 50 000 entries FYI). Quite often, Google cannot parse this XML file because it is truncated in the middle and the XML is therefore no longer valid. It seems I have the same issue when I browse this XML into Safari or Firefox. When I try a feed validator (http://validator.w3.org/feed/check.cgi), the test fails 8 times out of 10 and the source is clearly truncated.
>>
>> I tried to disable gzip encoding or to adapt quite a lot of settings. Nothing did the trick. Have U any idea that could help?
>> Thks a lot
>
> enable error_log at notice level (or higher) and see in logs when error occurs.
>
> --
> Anton Yuzhaninov
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://nginx.org/mailman/listinfo/nginx
More information about the nginx
mailing list