Eric Scheid wrote:
Would it be out of place to suggest text/plain as the recommended
content-type for this purpose? A short text/plain message can be fairly
easily displayed by an APP client in an error dialog.
and if the server wants to provide a link to an online FAQ or manual?
Nothing stopping them including that as text/html. There's also nothing
stopping them including a full PDF manual right there and then as
application/pdf. However it's rather pointless for a server to send back a
PDF document, or a lovely HTML error message with diagrams, link, and
background music if the client is just going to ignore it.
I was just suggesting a *recommendation* that might help with
interoperability. If you don't think that's necessary then leave the spec
wide open and let the market sort it out. However I suspect you'll end up
with servers returning whatever the hell they please, and clients just
ignoring everything because they don't know what to expect.
Regards
James
