Geek asks and answers

A few questions about the RESTful API and why some of the best practices are rarely implemented

In most manuals, documentation, articles, etc. about RESTful, I come across some of the same points, but still I have rarely ever seen these “What makes it RESTful” implemented.

For example, I read this many times:

  • Type of content

    Using HTTP Headers

    Accept: application/json, text/plain

    URL extension

    Not RESTful, URLs are not the place for Content-Type

I never came across an API where I saw this implemented. Every API I've ever used always required me to add XML or JSON to the end of the URL. Do they do it wrong?

  • Versioning

    Media Types Version

    Application / vnd.something.v1 + JSON

    Custom title

    X-API Version: 1

    URL version

    / v1 / Resouce Not RESTful, by placing the version in the URL, you create separate resources

, , , - ?

, API, , v1, v2 URL- (, google, imgur ..)

, API RESTful?

, .

+3
2

1) Accept URL-, , RESTful. , , .

2) v1/resource RESTful . URI RESTfulness. v1 URL-, , , . , URL . . RESTFul . , /resource/v2 .

, , REST, , , , REST, REST. , , RESTful. , . "RESTFul URL" - . "POST " - .

, REST, - - , - RESTful, , , . , .

+5

More articles:


All Articles