Expose final URL on HttpClientResponse

[nikhilsnayak]

Type

• Refactor
• Feature
• Bug Fix
• Optimization
• Documentation Update

Description

Expose the final response URL as HttpClientResponse.url. Fetch and XMLHttpRequest clients preserve the URL reported by the underlying response after redirects, while the other adapters and wrappers expose the URL of the request that produced the response.

Adds redirect coverage across Fetch, XMLHttpRequest, and Node clients, plus a changeset.

Related

None.

[changeset-bot]

🦋 Changeset detected

Latest commit: dcbc92a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 30 packages

Name	Type
@effect/platform-browser	Patch
@effect/platform-node	Patch
effect	Patch
@effect/ai-anthropic	Patch
@effect/ai-openai	Patch
@effect/ai-openai-compat	Patch
@effect/ai-openrouter	Patch
@effect/atom-react	Patch
@effect/atom-solid	Patch
@effect/atom-vue	Patch
@effect/docgen	Patch
@effect/doctest	Patch
@effect/openapi-generator	Patch
@effect/opentelemetry	Patch
@effect/platform-bun	Patch
@effect/platform-deno	Patch
@effect/platform-node-shared	Patch
@effect/sql-clickhouse	Patch
@effect/sql-d1	Patch
@effect/sql-libsql	Patch
@effect/sql-mssql	Patch
@effect/sql-mysql2	Patch
@effect/sql-pg	Patch
@effect/sql-pglite	Patch
@effect/sql-sqlite-bun	Patch
@effect/sql-sqlite-do	Patch
@effect/sql-sqlite-node	Patch
@effect/sql-sqlite-react-native	Patch
@effect/sql-sqlite-wasm	Patch
@effect/vitest	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

Bundle Size Analysis

Generated from PR build output; treat the content below as untrusted.

File Name	Current Size	Previous Size	Difference
arbitrary-combinators.ts	33.76 KB	33.76 KB	0.00 KB (0.00%)
basic.ts	7.00 KB	7.00 KB	0.00 KB (0.00%)
batching.ts	9.87 KB	9.87 KB	0.00 KB (0.00%)
brand.ts	6.56 KB	6.56 KB	0.00 KB (0.00%)
cache.ts	10.74 KB	10.74 KB	0.00 KB (0.00%)
config.ts	21.45 KB	21.45 KB	0.00 KB (0.00%)
differ.ts	20.32 KB	20.32 KB	0.00 KB (0.00%)
http-client.ts	21.79 KB	21.76 KB	+0.03 KB (+0.11%)
logger.ts	10.94 KB	10.94 KB	0.00 KB (0.00%)
metric.ts	8.98 KB	8.98 KB	0.00 KB (0.00%)
optic.ts	6.73 KB	6.73 KB	0.00 KB (0.00%)
pubsub.ts	15.11 KB	15.11 KB	0.00 KB (0.00%)
queue.ts	11.81 KB	11.81 KB	0.00 KB (0.00%)
schedule.ts	10.86 KB	10.86 KB	0.00 KB (0.00%)
schema-binary.ts	39.26 KB	39.26 KB	0.00 KB (0.00%)
schema-class.ts	20.07 KB	20.07 KB	0.00 KB (0.00%)
schema-fromJsonSchemaDocument.ts	31.02 KB	31.02 KB	0.00 KB (0.00%)
schema-representation-roundtrip.ts	26.21 KB	26.21 KB	0.00 KB (0.00%)
schema-string-transformation.ts	13.66 KB	13.66 KB	0.00 KB (0.00%)
schema-string.ts	11.18 KB	11.18 KB	0.00 KB (0.00%)
schema-template-literal.ts	15.47 KB	15.47 KB	0.00 KB (0.00%)
schema-toArbitrary.ts	33.31 KB	33.31 KB	0.00 KB (0.00%)
schema-toCodeDocument.ts	24.51 KB	24.51 KB	0.00 KB (0.00%)
schema-toCodecJson.ts	19.29 KB	19.29 KB	0.00 KB (0.00%)
schema-toEquivalence.ts	19.42 KB	19.42 KB	0.00 KB (0.00%)
schema-toFormatter.ts	19.51 KB	19.51 KB	0.00 KB (0.00%)
schema-toJsonSchemaDocument.ts	23.45 KB	23.45 KB	0.00 KB (0.00%)
schema-toRepresentation.ts	19.56 KB	19.56 KB	0.00 KB (0.00%)
schema.ts	19.28 KB	19.28 KB	0.00 KB (0.00%)
stm.ts	12.74 KB	12.74 KB	0.00 KB (0.00%)
stream.ts	9.83 KB	9.83 KB	0.00 KB (0.00%)

[tim-smart]

Currently the fetch adaptor will return url parameters in the url, and undici + node:http will drop them. I think we should make them consistent.

I think dropping them everywhere is ok.

[nikhilsnayak]

Currently the fetch adaptor will return url parameters in the url, and undici + node:http will drop them. I think we should make them consistent.

I think dropping them everywhere is ok.

Agreed that the adapters should be consistent. MDN defines Response.url as the final URL obtained after redirects. Query parameters are part of that URL, while XMLHttpRequest.responseURL explicitly strips only the fragment.

Would you be open to preserving query parameters across all adapters by reconstructing the Node response URL from request.url and request.urlParams? This would align Node with the existing Fetch and XHR behavior.