laravel route parameters with post routes vs post parameters

Question

Should route parameters only be used for get/delete requests? A user can join a challenge and I want to have an API endpoint for that.

Is this ok:

Route::post('/challenge/{challenge}/join', 'UserController@joinChallenge');

or should I rather pass the challenge id in the post body?

It doesn't matter if the users won't see it or it doesn't require SEO inspection. — Taha Paksu, Oct 24 '17 at 15:56
It's you who will see if the challenge uuid can be seen or not if it's ok to expose it to people then use URL parapeter else use a hidden field in the form !! — Maraboc, Oct 24 '17 at 15:57

score 2 · Answer 1 · answered Oct 24 '17 at 15:52

POST is a perfec solution: "Good Web design" requires non-idempotent actions to be sent via POST. This is a non-idempotent action(It has side effects, it modifyes the state of the DB).

Server logs don't record POST parameters, but they record urls. It's easier to look something through the logs with that design in your scenario.

idempotent: http://www.restapitutorial.com/lessons/idempotency.html

score 2 · Answer 2 · answered Oct 24 '17 at 16:31

It is ok

better way:

Route::post('/challenge/{challengeId}', 'UserController@joinChallenge');

don't forget to catch id in your controller

function joinChallenge(Request $request, $challangeId)

please see the reference below

What are the best/common RESTful url verbs and actions?

score 0 · Answer 3 · answered Oct 24 '17 at 15:57

0

you can pass parametres inside your url but you need to take accept this param by your method joinChallenge(Request $request, $challenge)

answered Oct 24 '17 at 15:57

Thamer

1,896
2
11
20

laravel route parameters with post routes vs post parameters

3 Answers3

Linked