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
Hi, we have problems with too large headers, namely cookies, that are being sent with every request although we don't need them as we sent Authorization bearer token in header as well. Using axios, there's no way to leave the cookies out, unless using recently added fetch adapter using native fetch for request which comes with limitation of HTTP/2 or QUIC protocol being used on server side for streaming.
Is there a way how to not store Next Auth cookies on client and use some other form of authorization/authentication?
we want to keep CredentialsProvider as an option which does not support "database" strategy
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, we have problems with too large headers, namely cookies, that are being sent with every request although we don't need them as we sent Authorization bearer token in header as well. Using axios, there's no way to leave the cookies out, unless using recently added fetch adapter using native fetch for request which comes with limitation of HTTP/2 or QUIC protocol being used on server side for streaming.
Is there a way how to not store Next Auth cookies on client and use some other form of authorization/authentication?
we want to keep CredentialsProvider as an option which does not support "database" strategy
Beta Was this translation helpful? Give feedback.
All reactions