You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:
Current behavior
I am not seeing HttpHeaders beeing saved or received in cache.
Expected behavior
HttpHeaders should be serialized as HttpHeaders otherwise a .get() wont longer work in interceptors.
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
We have request and correlation ids set in backend in response headers that I put into the response body for better access in templates. This is done in an interceptor.
Environment
Angular version: 17
Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
For Tooling issues:
- Node version: 20
- Platform: Mac
Others:
The text was updated successfully, but these errors were encountered:
I'm submitting a...
Current behavior
I am not seeing HttpHeaders beeing saved or received in cache.
Expected behavior
HttpHeaders should be serialized as HttpHeaders otherwise a
.get()
wont longer work in interceptors.Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
We have request and correlation ids set in backend in response headers that I put into the response body for better access in templates. This is done in an interceptor.
Environment
The text was updated successfully, but these errors were encountered: