Question 257826 in Laravel Question posted in
The official Laravel Documentation can be found here.

Laravel – Using headers to avoid unused arguments in function

In order to effectively use ACL in the system I am currently working on, I would need to send the same 2 URI parameters which are ids of the resources I want to check the users access against.

In order to avoid unused parameters in a number of functions, would it be considered okay practice to send these ids in the headers of his request?

I have attempted this and it works, however, I just need to know whether or not this is practice is considered okay

Tags:

2

Answers


  1. 0

    Custom headers in http requests are explicitly allowed, so in theory this practice should be considered "okay".

    The rest ist somewhat subjective and I wouldn’t consider it best practice to move information from the message body to the headers. In practice you could run into issues because of proxies / servers messing with the headers or control caching based on the body of requests (but not on the custom headers).

    Login or Signup to reply.
  2. 0

    The user id should be retrieved from the jwt token or from the session. Then you would not need the user id in the request.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search