GetStatusCode.com/494 will always return a 494 HTTP Status Code. That is by design.

494 Request Header Too Large (Nginx)

Client Error

The 4XX class of codes indicate you did something wrong. Specifically, there's an error on the client side.
Status Code Details, Courtesy of Wikipedia

Nginx internal code similar to 431 but it was introduced earlier in version 0.9.4 (on January 21, 2011).[original research?]

GetStatusCode Heatmap

Request Details

For easy reference, some of the details of your request have been included below.

IP Address Info

54.224.3.148

ec2-54-224-3-148.compute-1.amazonaws.com

  • Ashburn City
  • VA State
  • US Country
  • 39.0437 / -77.4875 Net Location

User Agent Info

CCBot/2.0 (http://commoncrawl.org/faq/)

GET

    POST

      About GetStatusCodes.com

      This is a tool that I built just to give me an easy way to test scripts that need to handle a variety of http status codes. Even if I'm not integrating with a REST API or other web service that might present a variety of status codes, I often still need to gracefully handle the occasional unexpected 500 error. Short of deliberately coding a glitch (which is only an option if I'm in control of the remote end, which isn't always the case), it's hard to test this. So, I wrote this handy site that responds with the appropriate header for the major codes.

      Whether you want to test code like I often do or just see an example 494 http status code, this is a handy tool to use. Plus, it offers some basic information that I occasionally need as well, like IP geolocation (and it even uses HTML5 geolocation to tell how far off they are from each other) and user agent parsing for browser and operating system.

      This tool is free to use, but you should be mindful of its limitations. It does not fully and properly implement the HTTP specification (it's not RESTful in the slightest). It only spits out this page (roughly, with some variation by code requested) and the associated HTTP status code headers. My scripts key off those response headers (as do most frameworks I've dealt with), so that's sufficient to test. But if you're expecting a 301 to actually include a Location header, you won't find it here.

      If you appreciate this tool, feel free to link to it, share it on Facebook, and the like. The more people use this, the more I can justify adding features.

      Recent Categories
      Recent Cities
      City Region Country Status Code
      Ashburn VA US 101 Switching Protocols
      Ashburn VA US 407 Proxy Authentication Required
      Ashburn VA US 405 Method Not Allowed
      Ashburn VA US 508 Loop Detected (WebDAV; RFC 5842)
      Ashburn VA US 307 Temporary Redirect
      Recent Operating Systems