Page Not Found

This blog is hosted on GoDaddy’s servers. For some of you, that’s all that needs to be said. For others, please read on to see how this may affect you and your use of the site.

There’s a slight chance that a “Page Not Found” error is not a legitimate error at this blog (no thanks to you know what and you know who). A URL like http://www.justoutsourcing.com/wp/fds45g612 will definitely generate a legitimate Page Not Found error, however our blog may present this error even when a URL like http://www.justoutsourcing.com/wp/about-us/ actually exists. The cause?

FastCGI and PHP.

FastCGI

FastCGI is a process that speeds up a website. It’s supposed to reduce server overhead, and thus adequately handle multiple page requests at once. The problem is that it doesn’t work very well with PHP-enabled content delivery systems. FastCGI is offered at GoDaddy, where this blog is hosted, but it isn’t required. So our stubborn use of it came down to two choices between consistency and speed. We could:

• discontinue the use of FastCGI for a consistent browsing experience.
• continue the use of FastCGI for a faster browsing experience.

We chose the latter since our blog is (1) a WordPress blog (slow), (2) hosted by GoDaddy (slow), and (3) function-dependent upon several plugins (slow). Discontinuing the use of FastCGI would have made this blog unbearably sluggish. So the consequence of our choice means that you may receive errors that don’t exist (see above).

Solution: Wait and Refresh

Until we find a suitable solution, this is the way it’s going to remain. If you run into a Page Not Found error that you don’t believe is legitimate, simply wait 1 – 2 seconds — then refresh the page. Your content will be delivered.

There’s not much more to say except sorry for the inconvenience and we’ll keep you updated on relevant changes.