Tag: server

Website Attack Recovery

Posted on July 24, 2006 in Websites by Jeff Starr

Recently, every website on our primary server was simultaneously attacked. The offending party indiscriminately replaced the contents of every index file, regardless of its extension or location, with a few vulgar lines of code, which indicated intention, identity, and influence.

Apparently, the attack occurred via Germany, through a server at the University of Hamburg. This relatively minor attack resulted in several hours of valuable online education. In this article, it is our intention to share experience with website attack recovery. This article is aimed at website developers, designers, and administrators.

Continue Reading

Perishable Press Server Migration

Posted on May 11, 2006 in Business, Perishable by Jeff Starr

As you may have read, we recently transferred our websites to a new server. Although the overall process went smoothly enough, several learning opportunities unfolded during the transfer of our humble Perishable Press website…

First, the setup. Perishable Press is a WordPress-powered website. On our previous server, we were running a Fantastico-installed WordPress version 2.0.2, upgraded from version 2.0. Permalinks were enabled and everything was running smoothly. Our database was only 13MB in size and around 12MB of that was disposable statistics information from WP-ShortStat and Bad Behavior. The crucial part of our database was a friendly 1MB in size.

Continue Reading

Server Migration Details

Posted on May 11, 2006 in Business, Perishable by Jeff Starr

About a year ago we signed up with a hosting provider that offered one of the best hosting deals around: lots of space, bandwidth, and transfer — plus all of the usual server software amenities that make life easier. Everything went smoothly at first…

In fact, the first six months of service were close to 100%. The few help-ticket items submitted were promptly resolved in a professional manner. We were ready to start some business and everything was going great. Then, about five months ago, we began noticing a serious increase in server downtime. Help tickets were also slow-going and the responses were like these cryptic one-liners that failed to address the actual problem, demonstrating a serious lack of concern and providing virtually no help. Further, multiple emails concerning account billing and renewal went (and remain) completely ignored. Indeed, email remains their only method of communication. At this point, we felt stranded, ignored, and utterly alone. Given this level of service, we were not comfortable hosting websites for our clients.

Continue Reading

HTTP Error Codes

Posted on April 3, 2006 in Function by Jeff Starr

A list of HTTP Error codes and corresponding definitions:

Informational Codes

  • 100 — Continue
  • 101 — Switching Protocols

Successful Client Requests

  • 200 — OK
  • 201 — Created
  • 202 — Accepted
  • 203 — Non-Authorative Information
  • 204 — No Content
  • 205 — Reset Content
  • 206 — Partial Content

Client Request Redirected

  • 300 — Multiple Choices
  • 301 — Moved Permanently
  • 302 — Moved Temporarily
  • 303 — See Other
  • 304 — Not Modified
  • 305 — Use Proxy
  • 307 — Temporary Redirect

Client Request Errors

  • 400 — Bad Request
  • 401 — Authorization Required
  • 402 — Payment Required (not used yet)
  • 403 — Forbidden
  • 404 — Not Found
  • 405 — Method Not Allowed
  • 406 — Not Acceptable (encoding)
  • 407 — Proxy Authentication Required
  • 408 — Request Timed Out
  • 409 — Conflicting Request
  • 410 — Gone
  • 411 — Content Length Required
  • 412 — Precondition Failed
  • 413 — Request Entity Too Long
  • 414 — Request URI Too Long
  • 415 — Unsupported Media Type
  • 416 — Requested Range Not Satisfiable
  • 417 — Expectation Failed

Server Errors

  • 500 — Internal Server Error
  • 501 — Not Implemented
  • 502 — Bad Gateway
  • 503 — Service Unavailable
  • 504 — Gateway Timeout
  • 505 — HTTP Version Not Supported