You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would expect the wildcard to return the larger result. As-is, RIPE's RDAP behavior is the opposite of ARIN's. The result is the same whether the asterisk is URL-encoded or not. I chose the non-encoded version since that is how the RFC specified the query.
The text was updated successfully, but these errors were encountered:
Given a wildcard query as described in:
https://datatracker.ietf.org/doc/html/rfc9082#section-3.2.3
for a query of the pattern:
https://rdap.db.ripe.net/entities?fn=DIGITALOCEAN*
there is only one result:
EH3832-RIPE
but the same query without the wildcard:
https://rdap.db.ripe.net/entities?fn=DIGITALOCEAN
returns a larger result:
I would expect the wildcard to return the larger result. As-is, RIPE's RDAP behavior is the opposite of ARIN's. The result is the same whether the asterisk is URL-encoded or not. I chose the non-encoded version since that is how the RFC specified the query.
The text was updated successfully, but these errors were encountered: