feat(http): add credentials support for fetch requests in httpResource #62390
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit adds support for the Fetch API's credentials option when using httpResource with the withFetch provider
thePunderWoman
approved these changes
Jul 1, 2025
Contributor
|
This PR was merged into the repository by commit b6ef428. The changes were merged into the following branches: main |
14 tasks
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, Angular's httpResource does not expose the credentials option from the underlying Fetch API.
Exposing this option would allow developers to explicitly control how cookies, authorization headers, and TLS client certificates are handled in cross-origin requests, aligning with security requirements and enabling better integration with external APIs.
New usage