-
-
Notifications
You must be signed in to change notification settings - Fork 508
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update sendRequest for axios to align on parameter deprecation (withCredentials) #2063
Comments
@evgarthub I think we'd want a separate parameter for this. It's a breaking change in Axios, therefore it should be a breaking change in this package, too. |
@mrlubos do you mean we should extend config with |
Sounds like it. I'd need to dig more into it, but if this feature is only available in Axios, config should also have that flag only when using Axios client. That's what it looks like to me right now |
I'm not able to run any tests, or rather they are failing because of #2052 issue (I'm on Windows). |
…-axios-to-align-on-parameter-deprecation-withcredentials fix: updated axios sendRequest (#2063)
@evgarthub The windows issue should be fixed in our fork https://github.com/hey-api/openapi-ts. We have also added support for interceptors, so if you would like to do something like this you can see examples in this ticket: |
Hi @jordanshatford ! Thanks for offering a solution! But it's already been fixed in this repo. |
@evgarthub yes, except it isn't actively maintained and still has many other bugs that are fixed in openapi-ts #2064 |
Hi @ferdikoomen!
Axios fixed vulnerability related to
withCredentials
request parameter by introducing new parameterwithXSRFToken
, details here:axios/axios#6046
GHSA-wf5p-g6vw-rhxx
Does it make sense to include new parameter next to
withCredentials
as author suggests?We verified internally that indeed passing both parameters with true value prevents client from behaving differently after axios update.
I will quickly create PR for it, let me know if it does make sense?
The text was updated successfully, but these errors were encountered: