* Clarify what values responseType can have in Node ( axios#2121) * Destroy stream on exceeding maxContentLength ( fixes axios#1098) ( axios#1485) * Makes Axios error generic to use AxiosResponse ( axios#1738) * docs(ECOSYSTEM): add axios-api-versioning ( axios#2020) * Fixing Mocha tests by locking follow-redirects version to 1.5.10 ( axios#1993) Add Querystring library note ( axios#1896) * Add react-hooks-axios to Libraries section of ECOSYSTEM.md ( axios#1925) has to be better way (within Did you find any better way than your workaround? I'm facing the same issue, and it's frustrating that I don't seem to be able to intercept the redirect and delete the Authorization header just for that follow-up / redirect request (to amazon in this case) 🤔
Same call with request api/postman/etc works. AWS S3 rejects call because two Authenication:.Redirect URL has a query string: X-Amz-Signature=blahblahblah appended. GET with header of Authorization: Bearer mytoken.Neither transformRequest, transformResponse,, appears to be able to allow me to inject myself into the process and temporarily remove the Authorization Header when hitting the redirection to AWS S3 - presumably if I could get in after a redirect I could do something to effect of delete headers.Authorization. Query string: X-Amz-Signature=blahblahblah.Redirect URL has a query string: X-Amz-Signature=blahblahblah appended.ĪWS S3 rejects call because two Authenication: GET with header of Authorization: Bearer mytoken I am running into rather similar situation but with a GET request: This is only applicable for request methods 'PUT', 'POST', 'PATCH' and 'DELETE'
0 kommentar(er)
