Currently songs can be requested through a simple GET request to
[...]/song/[id]/queue/. I guess everyone has seen this abused in the oneliner.
If this were changed to POST, that abuse could be limited. Since this doesn't
do any real harm I'd consider this to be low priority.
However, on the nitpicky side of things, HTTP GET request are specified as
"safe" in RFC 2616. This means that they should not have any side-effects. I
know everybody does it, but the semantics of a content retrieval request
changing the state of the application sounds just wrong to me. Nobody wants
their web app to behave like it was designed by Schroedinger. ;-)
Cheers,
Chocoholic
Original issue reported on code.google.com by Blames...@gmx.de on 3 Aug 2010 at 5:15
Original issue reported on code.google.com by
Blames...@gmx.de
on 3 Aug 2010 at 5:15