Incorrect Content-Type response header should not be a fatal error

[dsweet-mm]

Currently ~25% of IANA registered registrars and a significant number of registries cannot test for conformance at https://webrdapct.icann.org/ due to a response type of application/json instead of application/rdap+json. The error "Error code: 5 - A response was available to the tool, but the Content-Type is not application/rdap+JSON in the response." is immediately shown upon submitting an RDAP domain URL for testing.

There should be no reason this is a "fatal" error, but rather you should continue testing and roll it into the error array of the JSON results. As is, ICANN cannot get an accurate picture across-the-board of the level of industry conformance, but with this simple fix the picture would be drastically improved. Moreover, by making this error fatal, the tool is only adding barriers to progress for teams trying to comply, with no real upside.

[anewton1998]

I agree. This and the other non-fatal errors should be rolled into regular error codes.

In the mean-time, RDAP service operators may also use rdap-test and the rdap.org validator. While these tools aren't as comprehensive as this RDAP conformance tool, they'll help identify problems without blocking on the content-type.