REST Content-Type: Should it be based on extension or Accept header?

by

Both are valid. Quote from xml.com:

A resource may have more than one
representation. There are four
frequently used ways of delivering the
correct resource representation to
consumers:

  1. Server-driven negotiation. The service provider determines the right
    representation from prior knowledge of
    its clients or uses the information
    provided in HTTP headers like Accept,
    Accept-Charset, Accept-Encoding,
    Accept-Language, and User-Agent. The
    drawback of this approach is that the
    server may not have the best knowledge
    about what a client really wants.
  2. Client-driven negotiation. A client initiates a request to a
    server. The server returns a list of
    available of representations. The
    client then selects the representation
    it wants and sends a second request to
    the server. The drawback is that a
    client needs to send two requests.
  3. Proxy-driven negotiation. A client initiates a request to a server
    through a proxy. The proxy passes the
    request to the server and obtains a
    list of representations. The proxy
    selects one representation according
    to preferences set by the client and
    returns the representation back to the
    client.
  4. URI-specified representation. A client specifies the representation it
    wants in the URI query string.

More Related Contents:

  1. What exactly is RESTful programming?
  2. Best practices for API versioning? [closed]
  3. If REST applications are supposed to be stateless, how do you manage sessions?
  4. RESTful URL design for search
  5. Free Rest API to retrieve current datetime as string (timezone irrelevant) [closed]
  6. Design RESTful query API with a long list of query parameters [closed]
  7. Transactions in REST?
  8. How to QUEUE a new build using VSTS REST API
  9. What is RESTful programming?
  10. How to understand “RESTful API is stateless”?
  11. Groovy built-in REST/HTTP client?
  12. RESTful way to create multiple items in one request
  13. How to construct a REST API that takes an array of id’s for the resources
  14. Spring @ExceptionHandler does not work with @ResponseBody
  15. Why the slow WADL uptake? [closed]
  16. Azure Websites Kudu REST API – Authentication
  17. How to format Swagger 2.0 text descriptions?
  18. Update an entire resource collection in a REST way
  19. What are the best/common RESTful url verbs and actions?
  20. How should the header X-DocuSign-Authentication be used for REST and SOAP?
  21. Restful way for deleting a bunch of items
  22. When is it appropriate to respond with a HTTP 412 error?
  23. Swagger documentation with JAX-RS Jersey 2 and Grizzly
  24. How one could use server side sorting and paging with Azure Mobile Services
  25. Can I change the headers of the HTTP request sent by the browser?
  26. When in my REST API should I use an envelope? If I use it in one place, should I always use it?
  27. Swagger UI passing authentication token to API call in header
  28. The MAC signature found in the HTTP request ‘…’ is not the same as any computed signature
  29. Hyphen, underscore, or camelCase as word delimiter in URIs?
  30. REST API DESIGN – Getting a resource through REST with different parameters but same url pattern

Leave a Comment