Code 401 after updating from 3.40 to 3.8.0.

Question

Code 401 after updating from 3.40 to 3.8.0.

AlexanderN8 opened this issue 3 years ago · 4 comments

AlexanderN8 commented 3 years ago

After updating client-node version from 3.4.0 to 3.8.0 same code return:
Response was not statusCode 2XX, but was 401

Thank you.

Answer 1 · 2021-09-02T08:52:56.000Z

@AlexanderN8

Which version of Unleash are you using?

Can you share your configuration?

Answer 2 · 2021-09-02T09:01:56.000Z

fyo: until unleash-client 3.4 we used request module, which have been deprecated.

now unleash-client uses make-fetch-happen.

Can it be that you do any "request" magic behind the scenes?

Answer 3 · 2021-09-07T08:46:58.000Z

@ivarconr Thank you for the quick response. Indeed we have a proxy that adds tokens to headers. Is it really a different request from a proxy point of view?

Answer 4 · 2021-09-10T08:06:52.000Z

depends on how you intercept the call.