-
Notifications
You must be signed in to change notification settings - Fork 9
Other ‐ Common HTTP Problems
The following is a list of some common problems with RDAP services with regard to the use of HTTP.
RDAP servers are required to accept either the application/json or application/rdap+json media types,
but return only the application/rdap+json media type for RDAP responses. Testing with a bare web browser
(that is, a web browser not explicitly running an RDAP client) can sometime mislead operators into believing
their services are compliant.
See this information on media types.
The RDAP RFCs strongly recommend the use of HTTPS instead of HTTP, and the ICANN RDAP Technical Implementation Guide (TIG) requires the use of HTTPS and HTTPS only.
The "access-control-allow-origin" HTTP header is part of the Cross-Origin Resource Sharing (CORS) mechanism to help applications that run inside of web browsers to access web APIs, such as RDAP.
See this information on the access-control-allow-origin header.