Wow, it has been quite some time, and I JUST realized that you asked what I needed the behavior for.
I am working on a web service that needs to talk with a Flex application, which is a crippled client - it will not handle HTTP status codes correctly (among other things). At my company, we have defined a standard way to communicate with these crippled clients. One way is changing the Reason Phrase to "NOT OK" if the status code is a 400 or 500 series error, but still returning a 200 status code. ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2636944
