Skip to content
This repository has been archived by the owner on Jan 9, 2023. It is now read-only.

Do not use POST requests for everything #3

Closed
phanimahesh opened this issue Dec 5, 2015 · 6 comments
Closed

Do not use POST requests for everything #3

phanimahesh opened this issue Dec 5, 2015 · 6 comments
Labels

Comments

@phanimahesh
Copy link

Most routes are use HTTP POST even to fetch a resource, which does not conform to REST philosophy. They should be rewritten to use the appropriate HTTP verbs based on their function.

From a very cursory examination, /chkuser, /getuser and /allusers should be GET, /deleteusers should be DELETE and /updateuser should be a PUT/PATCH request.

The changes are minimal, I can submit a PR if you are interested.

@turboMaCk
Copy link
Contributor

I agree that using GET/PUT(or PATCH)/POST/DELETE is better for these and much more RESTlike. The question is how this will affect FE's adapter.

@phanimahesh
Copy link
Author

Which FE adapter are you referring to?

@jkleinsc
Copy link
Member

The routes in question are no longer needed on the server (see HospitalRun/hospitalrun-frontend@f185df1 and HospitalRun/hospitalrun-frontend@8b6a26d) and they will be removed from the server

@ghost
Copy link

ghost commented Oct 15, 2019

🎉 This issue has been resolved in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@ghost ghost added the released label Oct 15, 2019
@ghost
Copy link

ghost commented Oct 15, 2019

🎉 This issue has been resolved in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants