HTTP Status Codes
HTTP status codes that are used in reports provided by the BigDig. In general, positive values are the HTTP codes reported by the web server. Negative values indicate problems encountered at a lower level than the web server response. The negative codes along with some common HTTP codes are provided in the table below.
| Code | Description |
| -1 | Fatal, big problem trying to open connection |
| -2 | Processing of HTTP request failed for some reason |
| -3 | Socket read error |
| -4 | So.., HTTP worked but the response is empty |
| -5 | Uncaught IO error exception |
| -6 | Exception “Connection Refused” thrown |
| 200 | Everything’s great |
| 301 | Permanent redirect (update the source url!) |
| 302 | Temporary redirect (could be server maintenance) |
| 400 | *Bad Request (The request could not be understood by the server due to malformed syntax.) |
| 401 | Authorization required. The request requires user authentication. |
| 403 | Forbidden. The server understood the request, but is refusing to fulfill it. |
| 404 | Resource could not be found |
* A 400 error should not occur for DiGIR providers, as the default operation when resolving the endpoint URL should identical to a request for metadata.
