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
When a custom requestFactory adds a header to the request and the RequestEntity contains the same header (e.g. cookies), the one in the RequestEntity will take precedence.
Checking the code in InterceptingClientHttpRequest class:
Is this the desired behaviour? Would it be ok if the header values are added? What if the custom request factory wants to add a cookie and the request header adds a different cookie? (the last one will be in the header and the first one discarded)
Nestor Tarin Burriel opened SPR-15166 and commented
When a custom requestFactory adds a header to the request and the RequestEntity contains the same header (e.g. cookies), the one in the RequestEntity will take precedence.
Checking the code in
InterceptingClientHttpRequest
class:Is this the desired behaviour? Would it be ok if the header values are added? What if the custom request factory wants to add a cookie and the request header adds a different cookie? (the last one will be in the header and the first one discarded)
Kind regards,
Néstor
Affects: 4.2.6
Referenced from: commits 9243a14, e3be94c, 69c16f3
The text was updated successfully, but these errors were encountered: