Hi Luciano.
If I understand you thread correctly, i guess your logic won't fit. Laravel has no way to identify the difference between /{$token} and /about. He will likely try to match 'about' as a token.
I guess the best here for you is to set a second level of routing like:
/about /services /whatever-other-pages-you-need
and then: /token/{$token} or /user/{$token}
Like this, you won't have any conflict.
Hope it helps you,
Cheers
1
Maybe it would be better to store the token in a cookie or session variable, and inspect it's existence server-side. Another idea might be to pass the token as a get parameter, i.e. route?_token=your_token
0
Sign in to participate in this thread!
Moderators
-
driesvints
Joined 16 Dec 2013
-
joedixon
Joined 23 Jun 2014
-
tvbeek
Joined 8 Jan 2018
-
tomhatzer
Joined 28 Oct 2021
Laravel
Laravel News
Laracasts
Laravel Podcast