<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://www.websitemagazine.com/content/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>'Net Features : server response code</title><link>http://www.websitemagazine.com/content/blogs/posts/archive/tags/server+response+code/default.aspx</link><description>Tags: server response code</description><dc:language>en</dc:language><generator>CommunityServer 2008 SP2 (Build: 31104.93)</generator><item><title>Need To Know Server Response Code Ranges</title><link>http://www.websitemagazine.com/content/blogs/posts/archive/2008/08/15/need-to-know-server-response-code-ranges.aspx</link><pubDate>Fri, 15 Aug 2008 14:19:00 GMT</pubDate><guid isPermaLink="false">1e469e21-c924-44fa-a132-47b5d0a8ad47:5975</guid><dc:creator>Pete Prestipino</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://www.websitemagazine.com/content/blogs/posts/rsscomments.aspx?PostID=5975</wfw:commentRss><comments>http://www.websitemagazine.com/content/blogs/posts/archive/2008/08/15/need-to-know-server-response-code-ranges.aspx#comments</comments><description>&lt;p&gt;You may know what a 404 server response code means, but what about the 
others? Discover what all 200, 300, 400 and 500 code ranges mean and start 
understanding the information within your analytics solution for the betterment 
of your Web enterprise. You just might find a problem that can be easily 
corrected, but you&amp;#39;ll never know unless you look!&lt;/p&gt;
&lt;p&gt;&lt;b&gt;200-Level Codes (Success)&lt;/b&gt;&lt;br /&gt;
The two hundred range of server responses is reserved for successful responses. 
For example, the server response code 200 (OK) means the request was successful 
and information was returned. As you can imagine, this is the most commonly 
returned server response code.&lt;/p&gt;
&lt;p&gt;&lt;b&gt;300-Level Codes (Redirection)&lt;/b&gt;&lt;br /&gt;
The three-hundred level of codes indicates that further action from your browser 
is required. Two common codes (seen frequently in discussions about search 
engine optimization) are 300 and 301. A 301 response code means that the 
addressed source has moved permanently and all future requests should be made to 
the new URL. A 302 on the other hand means that the addressed resource has moved 
temporarily but future requests should continue to come to the original URL.&lt;/p&gt;
&lt;p&gt;&lt;b&gt;400-Level Codes (Client Error)&lt;/b&gt;&lt;br /&gt;
The four-hundred level codes indicate that some sort of error has happened. The 
most commonly seen 400-level response code is the 404, which means the resource 
(page) can not be found. There are many others 400-level codes however caused by 
client error. For example, a 410 code is more specific than 404 when a resource 
can&amp;#39;t be found. If the server knows that the resource is no longer available and 
no forwarding address is known then 410 should be returned. But 400-level 
response codes can be very specific (and helpful). For example, the 401 response 
code indicates a request is unauthorized, meaning the request requires some form 
of authentication such as a user ID and/or password. Since many response codes 
can be modified, this might be an excellent opportunity to present a password 
reminder message or password reset feature.&lt;/p&gt;
&lt;p&gt;&lt;b&gt;500-Level Codes (Server Error)&lt;/b&gt;&lt;br /&gt;
The five-hundred level codes indicate cases where the server knows it has made 
an error or is not capable of answering the request. (Mostly it means an error 
in server-side software). In most cases the server should include some 
information explaining the error and say if the situation is temporary or 
permanent. For example, 503 (Service Unavailable) is a code returned when the 
server cannot respond due to temporary overloading or maintenance. Some users, 
for example, have limited accounts which can only handle so many requests per 
day or bytes send per period of time. When the limits are exceeded a 503 code 
may be returned.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://www.websitemagazine.com/content/aggbug.aspx?PostID=5975" width="1" height="1"&gt;</description><category domain="http://www.websitemagazine.com/content/blogs/posts/archive/tags/servers/default.aspx">servers</category><category domain="http://www.websitemagazine.com/content/blogs/posts/archive/tags/server+response+code/default.aspx">server response code</category></item></channel></rss>