No we can get into an endless argument whether verbs are abused or not... IMHO, GET (as of today) gas the issue that it does not support a body. If I‘m executi

No we can get into an endless argument whether verbs are abused or not... IMHO, GET (as of today) gas the issue that it does not support a body. If I‘m executing a search (an idempodent action), how can I nicely pass a JSON object configuring the search? I‘ll just use POST for that... So then we‘re at the point where the url does not work anymore because we have a POST /findEmployee; POST /findContract; ... instead of GET /employee and GET /contract. Maybe I‘m wrong here, but it doesn‘t like nice in my eyes using POST in that way.