Comments on: Seamlessly switch off (and on) a Django (or other WSGI) site for upgrades http://www.caktusgroup.com/blog/2009/05/25/seamlessly-switch-off-and-on-a-django-or-other-wsgi-site-for-upgrades/ Blog | Django Web Development | Raleigh Durham Chapel Hill | Caktus Consulting Group Mon, 15 Mar 2010 02:24:51 +0000 http://wordpress.org/?v=2.6.3 By: tobias http://www.caktusgroup.com/blog/2009/05/25/seamlessly-switch-off-and-on-a-django-or-other-wsgi-site-for-upgrades/#comment-125 tobias Wed, 27 May 2009 13:20:10 +0000 http://www.caktusgroup.com/blog/?p=191#comment-125 That sounds reasonable, thanks. 405 Method Not Allowed sounded more permanent to me originally (see http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html), since POST <em>is normally</em> a valid method. From what I understand, most of the 4xx error codes can be either temporary or permanent, as long as the body indicates which it is. Post updated. That sounds reasonable, thanks. 405 Method Not Allowed sounded more permanent to me originally (see http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html), since POST is normally a valid method. From what I understand, most of the 4xx error codes can be either temporary or permanent, as long as the body indicates which it is. Post updated.

]]> By: masklinn http://www.caktusgroup.com/blog/2009/05/25/seamlessly-switch-off-and-on-a-django-or-other-wsgi-site-for-upgrades/#comment-122 masklinn Wed, 27 May 2009 09:23:31 +0000 http://www.caktusgroup.com/blog/?p=191#comment-122 I'd also suggest returning 405 Method Not Allowed rather than 403 Forbidden if the URL is called with something other than GET. I’d also suggest returning 405 Method Not Allowed rather than 403 Forbidden if the URL is called with something other than GET.

]]> By: tobias http://www.caktusgroup.com/blog/2009/05/25/seamlessly-switch-off-and-on-a-django-or-other-wsgi-site-for-upgrades/#comment-116 tobias Tue, 26 May 2009 15:44:13 +0000 http://www.caktusgroup.com/blog/?p=191#comment-116 Good call, thanks. I updated the code to return a 503 instead of a 200. Good call, thanks. I updated the code to return a 503 instead of a 200.

]]> By: Carl Meyer http://www.caktusgroup.com/blog/2009/05/25/seamlessly-switch-off-and-on-a-django-or-other-wsgi-site-for-upgrades/#comment-115 Carl Meyer Tue, 26 May 2009 15:35:35 +0000 http://www.caktusgroup.com/blog/?p=191#comment-115 Nice. It should return a 503 Service Unavailable status code rather than 200 OK, else you run the risk of a crawler indexing your "upgrading" page. Using the 503 status code won't affect browsers displaying the content of the temp page. If you really want to be HTTP-friendly, you'd optionally add a Retry-After header to indicate how long the maintenance is expected to take. Nice. It should return a 503 Service Unavailable status code rather than 200 OK, else you run the risk of a crawler indexing your “upgrading” page. Using the 503 status code won’t affect browsers displaying the content of the temp page.

If you really want to be HTTP-friendly, you’d optionally add a Retry-After header to indicate how long the maintenance is expected to take.

]]>