Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have the following REST API:
POST /users/martin/notify/...
The API is suppose to notify a list of users that the user Martin has something to say. The list of users to be notified can vary from 1 to a thousand. Where the list of a thousand users should be: Querystring, HTTP Header or the Request body? Why?
Request body. Headers and querystrings often have size limitations in practice that you would definitely hit with a thousand identifiers. At a more theoretical level, the request body should be the entity which you wish the server to process via POST. Headers are for protocol-level metadata about that entity; that is, information that helps the entity be processed, but not the entity itself. Querystrings are part of the identifier for the resource, and also not a representation of that resource.