News for hackers. Stuff that matters.
Re:Dropbox starts using POST, and why this is poor API design by wvenable on Monday March 02, 2015 @04:42PM (#9134530)
The alternative approach seems like a very complex way of solving the problem. Given the choice between that and POST, I'd choose POST every time.

I can't imagine the REPORT method is well supported and therefore will practically have the same limitations as POST or worse won't work at all.

Re:Dropbox starts using POST, and why this is poor API design by jbkkd on Monday March 02, 2015 @05:16PM (#9134720)
I agree. PHPBB has been using that since the dawn of time, and I always get confused looking at the url - there's no context to my search
Re:Dropbox starts using POST, and why this is poor API design by treve on Monday March 02, 2015 @04:51PM (#9134586)
It's actually quite well supported. In the same way that PATCH didn't suddenly cause issues everywhere. A HTTP-compliant actor must let through any method and most vendors seem to follow that rule quite well.
Re:Dropbox starts using POST, and why this is poor API design by wvenable on Monday March 02, 2015 @06:25PM (#9135091)
I'm not convinced that every firewall or proxy is HTTP-compliant either by accident or on purpose. And then even fully HTTP-compliant actors are unlikely to treat REPORT any differently from POST.