url.full is not PII (it's the URL path, not the query string), but it's now inside the if should_send_default_pii(): block, so it will never be set when PII is disabled — breaking span URL attribution in the default configuration.

When asgi_scope['type'] is not 'http' or 'websocket' (e.g. 'lifespan') and should_send_default_pii() is True, headers is undefined at headers.get('host') because it is only assigned inside the if ty in ('http', 'websocket'): block.

url.full is now only collected when PII is enabled, but _get_url explicitly does not include the query string (per its docstring: "without also including the querystring"), so it is not PII and should always be collected like other standard span attributes.

If _get_request_attributes is called with an ASGI scope whose type is not "http" or "websocket" (e.g. a future or custom type) and should_send_default_pii() is True, headers will be undefined when headers.get("host") is evaluated at line 130.

In sentry_sdk/integrations/_asgi_common.py (_get_request_attributes), the local headers is only assigned inside the if ty in ("http", "websocket"): block (line ~120), but the subsequent if should_send_default_pii(): block references headers.get("host") unconditionally when building url.full. For any ASGI scope type other than http/websocket (e.g., custom/proprietary scope types passed through the middleware), this raises NameError: name 'headers' is not defined. Reachability in practice is low because the ASGI spec only defines http, websocket, and lifespan, and lifespan is short-circuited in asgi.py:_run_app before reaching _get_request_attributes. Additionally, attempting to compute url.full for non-HTTP scope types is semantically questionable and likely should also be gated by the ty check.