Zwifi

Thanks for reporting this ! Indeed, I've been unlucky with headers in this library, this looks like a regression. I'll fix this very soon.

Can you give a try to the fix in https://github.com/inrupt/solid-client-authn-js/pull/1716 (by installing `@inrupt/solid-client-authn-browser@fixmangled-headers`) ? (or `@inrupt/solid-client-authn-node@fixmangled-headers`, depending on your use case)

Excellent ! I'll cut a patch release and close the issue when it ships. Thanks for following up !

Good question (he said, with a bit of a delay), I'll double-check.

Yep, I can reproduce. I'll see why this has regressed (again!)

What I'm seeing is that the following results in the headers being misssing: ``` fetch(resource, { headers: new Headers({ Accept: "text/turtle" }) }) ``` while this passes the headers through...

I'm sorry for the delayed response. That's a known issue that I'm planning on sorting out soon.

A bit late to the party, but this is fixed. I can't reproduce with the latest version of `@inrupt/solid-client-authn-browser`, so [`2.0.0`](https://github.com/inrupt/solid-client-authn-js/releases/tag/v2.0.0) is patched for sure, and I couldn't reproduce in...

It has been worked on in https://github.com/inrupt/solid-client-authn-js/pull/1556, but a lot happened in between and I never got around to merging it. I'll make sure it gets done soon.

Unfortunately, this would require non-trivial changes to the library, and it isn't on our short-term roadmap. I'll think about the design changes this entails though, and keep this issue updated...