> If you think (A) is the problem, then I think there's a > misunderstanding of HTTP responses. The Reason-Phrase is not mandated > to be anything in particular by the protocol---the client is not > required to even look at it and it can be replaced with anything. > http://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html
This is true in a strict technical-compliance sense. But the protocol also says "the Reason-Phrase is intended for the human user," suggesting that it should convey to a human what the code does to a machine. For error 500, it recommends "Internal Server Error". Without this least-astonishment principle, we could also look forward to creative stylings like "Error 404: File Found", "Error 401: Completely Authorized", and "Error 502: Hey, What's That Behind You?!?!" -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
