atom feed25 messages in ru.sysoev.nginxRe: How to solve the problem of "405 ...
FromSent OnAttachments
peacockMay 27, 2009 12:17 am 
Dave CheneyMay 27, 2009 12:28 am 
peacockMay 27, 2009 1:37 am 
Igor SysoevMay 27, 2009 1:45 am.Other
Rob SchultzMay 27, 2009 1:56 am 
peacockMay 27, 2009 2:37 am 
Igor SysoevMay 27, 2009 8:07 am 
peacockMay 27, 2009 9:14 am 
Cliff WellsJul 24, 2009 12:15 pm 
Igor SysoevJul 24, 2009 12:25 pm.Other
Jonathan VanascoJul 24, 2009 2:00 pm 
peacockJul 28, 2009 8:44 pm 
dennis caoOct 8, 2009 7:49 pm 
kleinchrisJan 29, 2010 8:29 am 
kleinchrisJan 29, 2010 8:41 am 
Nick PearsonJan 29, 2010 11:29 am 
Maxim DouninJan 29, 2010 2:03 pm 
Maxim DouninJan 29, 2010 2:12 pm 
kleinchrisJan 29, 2010 2:57 pm 
locojohnJul 6, 2011 4:28 pm 
locojohnJul 7, 2011 6:24 am 
ahuOct 6, 2011 9:20 am 
ahuOct 6, 2011 9:34 am 
fernandokoshJan 3, 2012 8:59 am 
goldenaxezMar 29, 2012 1:24 pm 
Subject:Re: How to solve the problem of "405 not allowed"?
From:Maxim Dounin (mdou@mdounin.ru)
Date:Jan 29, 2010 2:12:04 pm
List:ru.sysoev.nginx

Hello!

On Fri, Jan 29, 2010 at 11:41:43AM -0500, kleinchris wrote:

Can't edit my post... Here is a debug log, when i do it like this: error_page 405 =200 @405; location = @405 { root /var/www/vhosts/soulreafer; }

This will return internal 405 error page, as

1. you are serving request by static module again;

2. error_page to named location doesn't change request method.

Try this instead:

error_page 405 = $uri;

This way request method will be changed to GET, and the same uri will be used to serve it.

This log doesn't shows any problems, and it's not even for POST request. Instead it shows perfectly ok GET request (returning 304 not modified, as request includes If-Modified-Since).