-
Notifications
You must be signed in to change notification settings - Fork 24.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HttpRequest.clone forgets transferCache #54924
Comments
Hi All, |
Tell me if you need any help with this :) |
Fixes a bug where HttpRequest.clone() does not include the transferCache property. Fixes angular#54924.
Hello 👋🏻 I have opened PR #54939 that hopefully fixes the issue 🙂 Thanks for your help reviewing it ! |
Fixes a bug where HttpRequest.clone() does not include the transferCache property. Fixes angular#54924.
Fixes a bug where HttpRequest.clone() does not include the transferCache property. Fixes angular#54924.
Fixes a bug where HttpRequest.clone() does not include the transferCache property. Fixes angular#54924.
Fixes a bug where HttpRequest.clone() does not include the transferCache property. Fixes angular#54924.
Fixes a bug where HttpRequest.clone() does not include the transferCache property. Fixes angular#54924.
Fixes a bug where HttpRequest.clone() does not include the transferCache property. Fixes angular#54924.
Fixes a bug where HttpRequest.clone() does not include the transferCache property. Fixes angular#54924.
) Fixes a bug where HttpRequest.clone() does not include the transferCache property. Fixes angular#54924. PR Close angular#54939
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. |
Which @angular/* package(s) are the source of the bug?
common
Is this a regression?
No
Description
When cloning the HttpRequest, like keycloak does in it's interceptor, the clone-method forgets the transferCache-property.
The HttpRequest-constructor expects the transferCache to be set in the options-parameter, but the clone-method does not provide it.
This code should fix the problem.
`
const transferCache = update.transferCache || this.transferCache ;
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
No response
The text was updated successfully, but these errors were encountered: