unable to modify request header using an interceptor about fetch-client HOT 6 CLOSED

not that it should make a difference, but i use headers.set instead of append

from fetch-client.

not that it should make a difference, but i use headers.set instead of append

When using fetch-client it is headers.append and when using http-client it is headers.add but the problem here is that it seems like modification to the headers object which are done in an interceptor are ignored somehow.
Also it is strange that when i log the headers object with JSON.stringify then i see {} but when i log headers.url i see a url. This behaviour for me is a bit mystical.
Nevertheless i have not managed it to manipulate the request headers within an interception of the request. I know that in Angular it is no problem to do so :(
I just want to add Authorization: 'Bearer rz87rzr8z3...' to my headers.

from fetch-client.

@arnonuem look here https://github.com/SpoonX/aurelia-authentication/blob/master/src/fetchClientConfig.js

from fetch-client.

@Alexander-Taran i already did and found no symmantic difference there.

from fetch-client.

Also it is strange that when i log the headers object with JSON.stringify then i see {} but when i log headers.url i see a url. This behaviour for me is a bit mystical.

This is just how the Request object works in Chrome and maybe other browsers. It functions as a Map. JSON.stringify(new Map(['foo','bar'])) yields {} as well. If you want to log it, use JSON.stringify(Array.from(a.headers)).

https://developer.mozilla.org/en-US/docs/Web/API/Headers

from fetch-client.

It seems that request.headers.set( 'Authorization', 'Bearer ' + token ); seems to work. So i am closing this for now. Many thanks to @doktordirk and @davismj

from fetch-client.