Paths tend to be cached, parameters tend to not be, as a general rule.
So…
GET /customers/bob
vs
GET /customers?name=bob
The first is more likely to be cached (assuming proper headers, etc.) whereas the latter is likely not to be cached.
More Related Contents:
- RESTful Authentication
- RESTful URL design for search
- How can I handle many-to-many relationships in a RESTful API?
- What is the proper REST response code for a valid request but an empty data?
- HTTP response code for POST when resource already exists
- Security of REST authentication schemes
- How to make remote REST call inside Node.js? any CURL?
- Best practice for partial updates in a RESTful service
- What is the advantage of using REST instead of non-REST HTTP?
- Groovy built-in REST/HTTP client?
- Designing URI for current logged in user in REST applications
- Unable to upload zip file through karate framework
- API pagination best practices
- How to use cURL to send Cookies?
- Querystring in REST Resource url
- How to construct a REST API that takes an array of id’s for the resources
- Firefox Add-on RESTclient – How to input POST parameters?
- Making a PowerShell POST request if a body param starts with ‘@’
- Spring 4 RestController JSON: characteristics not acceptable according to the request “accept” headers
- Jersey with Struts2 [duplicate]
- REST API Authentication
- Should I use Singular or Plural name convention for REST resources?
- How to download excel (.xls) file from API in postman?
- Where can I find jenkins restful api reference? [closed]
- Is it correct to return 404 when a REST resource is not found?
- When is it appropriate to respond with a HTTP 412 error?
- Websocket vs REST when sending data to server
- ‘Best’ practice for restful POST response
- When in my REST API should I use an envelope? If I use it in one place, should I always use it?
- Swagger UI passing authentication token to API call in header