REST lesson learned: Avoid user supplied data in URI segments
In the end, we used a third alternative: we assigned an internal ID to all tags and mapped back and forth so that the URL for the "sticky & sweet" tag became http://foo.ploeh.dk/api/tags/1234
. Yes: that makes it impossible to guess the URL, but we were building a level 3 RESTful API, so clients are expected to follow links - not guess the URL.
Read full article from REST lesson learned: Avoid user supplied data in URI segments
No comments:
Post a Comment