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
{{ message }}
Repository navigation
Commit b6777c8
Browse filesBrowse the repository at this point in the historyBrowse files
Fix: RDAP referral behind a proxy, private address check for NAT64/6to4
- If the referral goes through the system proxy, the host name is not
resolved locally (the proxy resolves it), so referrals work in
networks where only the proxy resolves public names. IP addresses in
the URL are still checked.
- The private address check also covers IPv6 addresses that contain an
IPv4 address (NAT64 64:ff9b::/96, 6to4 2002::/16), the rest of
64:ff9b::/32 (local-use NAT64), 192.0.0.0/24 and 198.18.0.0/15.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: Website/docs/application/rdap.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -123,7 +123,7 @@ For many domains (e.g. `.com` and `.net`), the registry only returns basic data
123
123
124
124
:::note
125
125
126
-
For security reasons, a referral is only followed if it uses HTTPS and does not point to a local or private address (e.g. `192.168.0.0/16`). Otherwise, a message is shown and only the result of the registry is displayed.
126
+
For security reasons, a referral is only followed if it uses HTTPS and does not point to a local or private address (e.g. `192.168.0.0/16`). Otherwise, a message is shown and only the result of the registry is displayed. If a proxy is configured in Windows, the proxy resolves the host name of the referral, so it is only checked if it is an IP address.
0 commit comments