Fatcow Server Upgrade and WordPress

  • If you have an account at Fatcow, you probably know that they are upgrading their servers. There are a few problems I ran into, that probably affect all other users as well. In short:

    — The server’s directory structure has changed. Update your file upload destination directory in the control panel.

    — wp-blog-header.php sets a “Last Modified” header, instead of “Last-Modified”. The new server doesn’t like that. You’ll get “500 Internal Server Error” responses if you try to access your RSS feeds.

    — One problem I haven’t been able to fix yet is with rewrites. The new server forces a browser redirect, which puts all the PHP junk into the address bar.

    For a bit more detail, take a look at my blog under Fatcow Server Upgrade and WordPress.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter kas

    (@kas)

    Fatcow support told me that the rewrite issue is a problem caused by the new server configuration, and can’t be fixed for now.
    [my reaction] Too bad, but not exactly a show stopper.

    Moderator James Huff

    (@macmanx)

    Perhaps they’ve upgraded to Windows Servers rather than Apache Servers? That would break mod_rewrite.

    Thread Starter kas

    (@kas)

    No, mod_write works as it’s supposed to. The problem is that after it rewrites the URL, the server config forces a hard redirect.

    I was told this is being done because PHP and static content are served from different servers. So if it looks like a static HTML page and then gets rewritten, the server has to do an external redirect to another box. Poor design choice for load balancing (or security for that matter). Hopefully enough people will complain, and they’ll fix it.

    Other than that, WP runs fine.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Fatcow Server Upgrade and WordPress’ is closed to new replies.