Geek Answers Handbook

RESTful processing function / resource: GET or POST?

I am creating a RESTful web service, and some resources are computational or processing functions. For example, a user can scale and transform images through an API by sending an image and receiving a scaled or transformed image back.

According to section 2.5 of the RESTful Web Services Cookbook , I have to use GET:

Treat the processing function as a resource, and use HTTP GET to fetch a
representation containing the output of the processing function. Use query
parameters to supply inputs to the processing function.

This is clear for cases where the inputs are simple (for example, the long / lat-coordinates of a point). However, should I follow the same advice for larger input data such as images? As far as I know, it is impossible to send this data as a request parameter.

+5
source share
4

POST. . , .

+6

- . PUT, , GET , , .

+1

Due to the limitations of the HTTP protocol, I advise against it. This is a very valid very viable example of the exception that must be made for this rule.

0
source

Check out this link http://support.microsoft.com/default.aspx?scid=KB;en-us;q208427 . It states that the maximum URL for IE is 2083 characters.

0
source

More articles:


All Articles