Unauthorized errors when using openapi-fetch with SvelteKit about openapi-typescript HOT 3 OPEN

Thanks for the reproduction! In your code the fact that you aren’t explicitly setting the Authorization header on GET means that it’s not there.

Even if you supply a custom fetch() function, that’s just the wrapper that gets called; openapi-fetch still assembles the headers and actually fires off the request. So it doesn’t know about any headers that may/may not have been set in SvelteKit.

But that said, I’m open to proposals if there’s some way openapi-fetch could know what headers SvelteKit had set somehow?

from openapi-typescript.

In your code the fact that you aren’t explicitly setting the Authorization header on GET means that it’s not there.

I guess that makes sense. Though I would have expected it to use the headers set by SvelteKit on its custom fetch() function. I'm not sure how that actually works so I don't know how to improve it. It would be great if this library would support the use case though. I guess we would have to understand how this is handled and then see if it can be taken advantage of when making the final request.

from openapi-typescript.

openapi-fetch still assembles the headers and actually fires off the request

I just had another look at the code and from what I understand this is not entirely correct. After openapi-fetch fires of the request it is intercepted by SvelteKit in its handleFetch() function. The console logs here then show that an Authorization header is set. It still fails and I don't know why.

from openapi-typescript.