4 ms·
Ah interesting, so you're saying that GMail is not likely to be avoiding the POST requests if they're in the JS code? I have a passing, non-professional famili
by wutbrodo 5y ago
Ah interesting, so you're saying that GMail is not likely to be avoiding the POST requests if they're in the JS code? I have a passing, non-professional familiarity with Web practices, so this isn't something I have a great intuition for.
- nickjj 5y agoThe basic flow would be: - You GET /reset/abc123 - Your server responds back with a page that has a form - There's a hidden field with the token - Javascript kicks in and on page load executes the form as a POST request - Your server responds to that POST request and does whatever it needs to do All of that is kicked off by gmail visiting /reset/abc123, and now it comes down to whether or not gmail's pre-visiting code will run the JS on the page. If not, then the above workflow fixes this issue, if it does then you're in the same position as avoiding all of this and having a GET /reset/abc123 perform the destructive action.
- wutbrodo 5y agoRight, it's the second part of the fourth bullet that I was asking about. Basically, that it sounds like it isn't feasible for Google to avoid POST requests if they're being submitted from JS.