See associated pull request for more information.

See associated pull request for more information.

See associated pull request for more information.

See associated pull request for more information.

See associated pull request for more information.

See associated pull request for more information.

See associated pull request for more information.

See associated pull request for more information.

See associated pull request for more information.

Adds more detailed descriptions for the `assets` and `outputHashing` options in the `@angular/build:application` builder's schema. This improves clarity for users configuring these options.

Closes #31477

(cherry picked from commit 2a1667f)

…lder options

Adds more detailed descriptions for the `assets` and `outputHashing` options in the `@angular-devkit/build-angular:browser` builder's schema. This improves clarity for users configuring these options.

(cherry picked from commit 00b7d74)

(cherry picked from commit 6fb85b2)

See associated pull request for more information.

See associated pull request for more information.

See associated pull request for more information.

A request with a specially crafted URL starting with a double slash (e.g., `//example.com`) could cause the server-side rendering logic to interpret the request as being for a different host. This is due to the behavior of the `URL` constructor when a protocol-relative URL is passed as the first argument.

This vulnerability could be exploited to make the server execute requests to a malicious domain when relative paths are used within the application (e.g., via `HttpClient`), potentially leading to content injection or other security risks.

The fix ensures that the request URL is always constructed as a full URL string, including the protocol and host, before being passed to the `URL` constructor. This prevents the host from being overridden by the path.

Closes #31464

(cherry picked from commit 7be6c8f)