-
-
Notifications
You must be signed in to change notification settings - Fork 403
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
Ingredient edition does refused from JS #9807
Comments
It looks like Hunger Games/the browser isn't sending the user's cookies when executing the POST request. Calling the API manually also doesn't work if you're not signed in with an OFF account. The browser is sending a pretty weird request from the {"withCredentials":true} I don't think the old {
credentials: 'include'
} or {
credentials: 'same-origin'
} in the I think #525 could be better with APIv3, and the old APIs probably won't be changed that drastically for backwards compatibility. |
|
Thanks for the debug. I may have gone lost wen trying get/post/patch and other to make it works 😅 Effectively, it works better with the |
Thanks for the help, it's working now 👍 🎉 |
What
When sending a request to edit an ingredient text, the request is refused. However the same request copy pasted in the browser succeed
Steps to reproduce the behavior
"no code or invalid code"
"fields saved"
Expected behavior
"fields saved"
Why
Screenshot/Mockup/Before-After
Part of
Additional context
Type of device
Number of products impacted
Time per product
The text was updated successfully, but these errors were encountered: