> Years of experience in protocol implementation have made me a firm believer in Murphy's
> Law. As a Printer implementor I want to avoid any risk of crashing the server at all costs.
> If a client sends me a malformed request, I don't trust that client and I don't want to have
> anything more to do with its request as soon as I have determined that it is bad. Hopefully
> this is a rare occurence anyway, so why try to optimize the quality of the response? In
> production systems, users should never get "client-error-bad-request" responses, anyway.
>> -Carl
Is a message that specifies an operation that the server doesn't support a malformed request?
-Hugo