Infrastructure

A couple items on the exception handling page seem to be problematic:
http://mule1.dataone.org/ArchitectureDocs-current/apis/Exceptions.html

1. In the HTTP Error Handling Codes table, the "<100 error" category is redundant with 500 errors, and should be removed. We currently use the detailCode to describe and pinpoint local errors. (we also set HTTP status codes for problems outside the transmission protocol.)

2. Under the general section, the last paragraph is vague, especially with regard to the value of HTTP status. Because it is highly advantageous for the clients to rely on the HTTP status to determine what is in the response stream (especially java, to avoid buffering large files), the request is to assert in the documentation a guarantee that if a d1 error is returned, the HTTP status matches the value of the errorCode attribute.