Yes, it is not complete. Sorry, i thought that was enough. Here is my
full config for "server":

server {
server_name agenciaperu.tv;

access_log /path/to/logs/access.log;
error_log /path/to/logs/error.log;

root /path/to/htdocs;
index index.html;

error_page 403 404 /404/;
error_page 502 503 504 /500/;

location = /404/ { internal; }
location = /500/ { internal; }

location / {
fastcgi_pass unix:/tmp/fcgi-process.sock;

include fastcgi_params;

fastcgi_param PATH_INFO $fastcgi_script_name;
}
}

I'll make a change to server 50x errors with a static file.

Thanks!

El 09/10/2009, a las 14:33, Igor Sysoev escribió:

> On Fri, Oct 09, 2009 at 12:20:29PM -0500, Fernando Flórez wrote:
>
>> Not physically. The /404/ folder is mapped to a fastcgi process
>> (django url).
>
> So is this incomplete configuration ?
> I could not reproduce the issue.
>
> BTW, 502-504 errors should be handled by static files, since there is
> big chance to get another 502/504 error while handling them using
> fastcgi.
>
>> El 09/10/2009, a las 11:53, Igor Sysoev escribió:
>>
>>> On Fri, Oct 09, 2009 at 10:05:36AM -0500, Fernando Flórez wrote:
>>>
>>>> It is.
>>>>
>>>> server {
>>>> server_name mydomain.com;
>>>>
>>>> access_log /path/to/logs/access.log;
>>>> error_log /path/to/logs/error.log;
>>>>
>>>> root /path/to/website/htdocs;
>>>> index index.html;
>>>>
>>>> error_page 403 404 /404/;
>>>> error_page 502 503 504 /500/;
>>>>
>>>> location = /404/ { internal; }
>>>> location = /500/ { internal; }
>>>> }
>>>
>>> Does /path/to/website/htdocs/404/index.html exist ?
>
>
> --
> Igor Sysoev
> http://sysoev.ru/en/
>