SitePoint Sponsor

User Tag List

Results 1 to 10 of 10
  1. #1
    SitePoint Guru pinch's Avatar
    Join Date
    Mar 2005
    Posts
    688
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    app_offline.htm & HTTP Status Code

    I need to take down my site for awhile but don't want the web crawlers to think the pages are unavailable. I normally use app_offline.htm to bring down my site but I'm seeing conflicting information as to what HTTP Status Code is presented. My understanding is that you should use status code 503 to tell the crawlers the page is temporarily unavailable, but some resources say that this results in a 404 status code to be presented?

  2. #2
    SitePoint Author silver trophybronze trophy
    wwb_99's Avatar
    Join Date
    May 2003
    Location
    Washington, DC
    Posts
    10,653
    Mentioned
    4 Post(s)
    Tagged
    0 Thread(s)
    How long? Hours? Days? Weeks?

  3. #3
    SitePoint Guru pinch's Avatar
    Join Date
    Mar 2005
    Posts
    688
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by wwb_99 View Post
    How long? Hours? Days? Weeks?
    Let's say 2 days.

  4. #4
    SitePoint Author silver trophybronze trophy
    wwb_99's Avatar
    Join Date
    May 2003
    Location
    Washington, DC
    Posts
    10,653
    Mentioned
    4 Post(s)
    Tagged
    0 Thread(s)
    I'd do something a bit fancier than app_offline.htm that returns the right status codes then -- that is for a quick fix when you want to stop things from banging the app while you update, not for extended downtime.

    Really I'd find a way to avoid extended downtime, but I've spent too long in operations . . .

  5. #5
    SitePoint Guru pinch's Avatar
    Join Date
    Mar 2005
    Posts
    688
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by wwb_99 View Post
    I'd do something a bit fancier than app_offline.htm that returns the right status codes then -- that is for a quick fix when you want to stop things from banging the app while you update, not for extended downtime.

    Really I'd find a way to avoid extended downtime, but I've spent too long in operations . . .
    That makes sense and I agree, I just didn't know if there was a way to extend downtime and still not be penalized by the SEs. Thanks.

  6. #6
    SitePoint Guru pinch's Avatar
    Join Date
    Mar 2005
    Posts
    688
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by wwb_99 View Post
    I'd do something a bit fancier than app_offline.htm that returns the right status codes then -- that is for a quick fix when you want to stop things from banging the app while you update, not for extended downtime.

    Really I'd find a way to avoid extended downtime, but I've spent too long in operations . . .
    So are you saying that app_offline.htm returns the correct 503 HTTP status code? Also, how long do you think it is appropraite to have a site down for upgrade using app_offline.htm?

  7. #7
    SitePoint Author silver trophybronze trophy
    wwb_99's Avatar
    Join Date
    May 2003
    Location
    Washington, DC
    Posts
    10,653
    Mentioned
    4 Post(s)
    Tagged
    0 Thread(s)
    Honestly no idea what code -- really don't use it, we swap versions so our site might blip for 5 seconds. As for extended downtime, I'm generally in the school of thought that you shouldn't have downtime longer than that in the modern era.

  8. #8
    SitePoint Guru pinch's Avatar
    Join Date
    Mar 2005
    Posts
    688
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    I hear ya. Normally my upgrades don't take that long but this one involves wholesale DB modifications and blog integration which will take awhile.

    What do you mean by swap versions?

  9. #9
    SitePoint Author silver trophybronze trophy
    wwb_99's Avatar
    Join Date
    May 2003
    Location
    Washington, DC
    Posts
    10,653
    Mentioned
    4 Post(s)
    Tagged
    0 Thread(s)
    Could be lots of things. First, those sorts of things happen in QA/staging here. By the time we hit production, it is really a matter of svn switch + run the database update script. Some crazier things have involved swapping out entire VMs. And we've started using some http reverse proxies so swapping can then become switching what the proxy is forwarding to. Meaning upgrades are completely non destructive.

  10. #10
    SitePoint Guru pinch's Avatar
    Join Date
    Mar 2005
    Posts
    688
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by wwb_99 View Post
    Could be lots of things. First, those sorts of things happen in QA/staging here. By the time we hit production, it is really a matter of svn switch + run the database update script. Some crazier things have involved swapping out entire VMs. And we've started using some http reverse proxies so swapping can then become switching what the proxy is forwarding to. Meaning upgrades are completely non destructive.
    We do a similar thing here at work but unfortunately I'm talking about a personal project. Thanks for the advice.


Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •