4xx Client Error « Applying the Web to Enterprise IT

4xx Client Error

HTTP is actually quite clear on how decoupled the server is from the client by calling all non-technical errors simply Client Errors. Dang! So simple! 404 – who broke the contract? The client! 406 – who broke the contract? The client! …

RFC2616 uses a softer tone though:

“The 4xx class of status code is intended for cases in which the client seems to have erred.”

I guess testing a RESTful system means testing the clients…

This entry was posted on Monday, January 25th, 2010 at 6:51 pm and is filed under Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

One Response to “4xx Client Error”

Tweets that mention 4xx Client Error « Applying the Web to Enterprise IT -- Topsy.com says:

January 26, 2010 at 7:55 am

[...] This post was mentioned on Twitter by Erik Wilde and Jan Algermissen, Graham Moore. Graham Moore said: RT @algermissen: Who's to blame for any 4xx? The client! :-) http://www.nordsc.com/blog/?p=142 [...]

Leave a Reply