> > Perhaps, but that shouldn't be for you^D^D^DJerome to decree.
Fixed that for ya. :-) In my case, we're dealing with a custom server and a custom client > that talk only to each other. Then my comment about intermediaries obviously does not apply to your case. Custom HTTP status codes should be avoided "in the wild" where they may confuse proxies and UAs whose authors may not have read the spec very carefully, of which there are regrettably many. That, plus what Joshua Tuberville > quoted from RFC 2616: > > > ... applications MUST understand the class of any status code, as > > indicated by the first digit, and treat any unrecognized response > > as being equivalent to the x00 status code of that class > > Note the use of the word "MUST". Hence, Restlet is NOT in compliance > with the RFC. I would consider this a bug. Yes, I believe you are right, please file it if you have not done so already. I don't know that it would be intuitive for isSuccess to be true for 1xx or 3xx. I think of the success codes as the 2xx series exclusively (cf. the language previously cited). - R
