Skip to content

Commit eb61cee

Browse files
committed
docs: record why the WireServer block is load-bearing
1 parent 4f61f67 commit eb61cee

1 file changed

Lines changed: 7 additions & 1 deletion

File tree

python/semantic_kernel/connectors/openapi_plugin/server_url_validator.py

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,13 @@
1717
DEFAULT_ALLOWED_SCHEME = "https"
1818

1919
# Azure instance metadata service (WireServer). Unlike the AWS/GCP equivalents, this
20-
# address is publicly routable, so it would otherwise pass the private-address checks.
20+
# address is publicly routable, so it would otherwise pass the private-address checks:
21+
# 168.63.129.16 has is_private=False and is_link_local=False, so no generic rule
22+
# catches it - not even after NAT64 decoding (64:ff9b::a83f:8110 decodes to exactly
23+
# this address and would sail through the private/link-local branches). The explicit
24+
# entry below is therefore load-bearing, not redundant with the range checks; do not
25+
# remove it on the assumption that "the private-address branch already covers Azure
26+
# metadata".
2127
_AZURE_WIRE_SERVER = ipaddress.ip_address("168.63.129.16")
2228
_AZURE_WIRE_SERVER_CATEGORY = "Azure metadata (WireServer)"
2329

0 commit comments

Comments
 (0)