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
Thanks for raising. I think expecting these values to not bleed into other requests is totally reasonable. I think those body headers could just be merged without merging them into the instance-level headers, but I worry that some might rely on this bug being there. I think we'll have the same problem as deletes as well.
Not ideal but, for now, you're able to clear the offending headers between requests using:
Describe the problem
GET requests are mutating the shared headers causing parameters to leak into subsequent requests.
Relevant code where the headers are being mutated.
ruby-auth0/lib/auth0/mixins/httpproxy.rb
Lines 75 to 76 in afc87a0
Is there any reason why
headers.merge(params: body)
would not be used instead?What was the expected behavior?
I would expect parameters from a GET request to not leak into subsequent POST/PATCH requests.
Reproduction
Environment
ruby-auth0/lib/auth0/mixins/httpproxy.rb
Lines 75 to 76 in afc87a0
The text was updated successfully, but these errors were encountered: