You should use hyphens in a crawlable web application URL. Why? Because the hyphen separates words (so that a search engine can index the individual words), and a hyphen is not a word character. Underscore is a word character, meaning it should be considered part of a word. Double-click this in Chrome: camelCase Double-click this … Read more
The reason you get no hard answers is because there is no hard RESTful standard. So I can only suggest that you create a hard standard and stick to it within your own APIs I used this as a guide for RESTful services http://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api It says respond with a 204 status and an empty body … Read more
With this configuration Struts2 filter intercepts all requests. To exclude your /service/* requests use struts.action.excludePattern constant: <constant name=”struts.action.excludePattern” value=”/service/.*” />
In Spring 3.1 a preferred way to control this behaviour is to add a RedirectAttributes parameter to your method: @RequestMapping(“save/”) public String doSave(…, RedirectAttributes ra) { … return “redirect:/success/”; } It disables addition of attributes by default and allows you to control which attributes to add explicitly. In previous versions of Spring it was more … Read more
I have been doing some extensive research into this and other REST paging related questions lately and thought it constructive to add some of my findings here. I’m expanding the question a bit to include thoughts on paging as well as the count as they are intimitely related. Headers The paging metadata is included in … Read more
General principles for good URI design: Don’t use query parameters to alter state Don’t use mixed-case paths if you can help it; lowercase is best Don’t use implementation-specific extensions in your URIs (.php, .py, .pl, etc.) Don’t fall into RPC with your URIs Do limit your URI space as much as possible Do keep path … Read more
Best practice for RESTful API design is that path params are used to identify a specific resource or resources, while query parameters are used to sort/filter those resources. Here’s an example. Suppose you are implementing RESTful API endpoints for an entity called Car. You would structure your endpoints like this: GET /cars GET /cars/:id POST … Read more