> Symfony 6 > Harmonious Development with Symfony 6
13.

Smart Routes: GET-only & Validate {Wildcards}

|

Share this awesome video!

|

Now that we have a new page, at your terminal, run debug:router again.

php bin/console debug:router

Yep, there's our new endpoint! Notice that the table has a column called "Method" that says "any". This means that you can make a request to this URL using any HTTP method - like GET or POST - and it will match that route.

Restricting Routes to GET or POST Only

But the purpose of our new API endpoint is to allow users to make a GET request to fetch song data. Technically, right now, you could also make a POST for request to this... and it would work just fine. We might not care, but often with APIs, you'll want to restrict an endpoint to only work with one specific method like GET, POST or PUT. Can we make this route somehow only match GET requests?

Yep! By adding another option to the Route. In this case, it's called methods, it even auto-completes! Set this to an array and, put GET.

25 lines | src/Controller/SongController.php
<?php
// ... lines 3 - 9
class SongController extends AbstractController
{
#[Route('/api/songs/{id}', methods: ['GET'])]
public function getSong($id): Response
{
// ... lines 15 - 22
}
}

I'm going to hold Command and click into the Route class again... so we can see that... yup! methods is one of the arguments.

Back over on debug:router:

php bin/console debug:router

Nice. The route will now only match GET requests. It's... kind of hard to test this, since a browser always makes GET requests if you go directly to a URL... but this is where another bin/console command comes in handy: router:match.

If we run this with no arguments:

php bin/console router:match

It gives us an error but shows how it's used! Try:

php bin/console router:match /api/songs/11

And... that matches our new route! But now ask what would happen if we made a POST request to that URL with --method=POST:

php bin/console router:match /api/songs/11 --method=POST

No routes match this path with that method! But it does say that it almost matched our route.

Restricting Route Wildcards by Regex

Let's do one more thing to tighten up our new endpoint. I'm going to add an int type-hint to the $id argument.

25 lines | src/Controller/SongController.php
<?php
// ... lines 3 - 9
class SongController extends AbstractController
{
#[Route('/api/songs/{id}', methods: ['GET'])]
public function getSong(int $id): Response
{
// ... lines 15 - 22
}
}

That... doesn't change anything, except that PHP will now take the string id from the URL that Symfony passes into this method and cast it into an int, which is... just nice because then we're dealing with a true integer in our code.

You can see the subtle difference in the response. Right now, the id field is a string. When we refresh, id is now a true number in JSON.

But... if somebody was being tricky... and went to /api/songs/apple... yikes! A PHP error, which, on production, would be a 500 error page! I do not like that.

But... what can we do? The error comes comes from when Symfony tries to call our controller and passes in that argument. So it's not like we can put code down in the controller to check if $id is a number: it's too late!

So what if, instead, we could tell Symfony that this route should only match if the id wildcard is a number. Is that possible? Totally!

By default, when you have a wildcard, it matches anything. But you can change it match a custom regular expression. Inside of the curly braces, right after the name, add a < then > and, in between, \d+. That's a regular expression meaning "a digit of anything length".

25 lines | src/Controller/SongController.php
<?php
// ... lines 3 - 9
class SongController extends AbstractController
{
#[Route('/api/songs/{id<\d+>}', methods: ['GET'])]
public function getSong(int $id): Response
{
// ... lines 15 - 22
}
}

Try it! Refresh and... yes! A 404. No route found: it simply didn't match this route. A 404 is great... but a 500 error... that's something we want to avoid. And if we head back to /api/songs/5... that still works.

Next: if you asked me what the most central and important part of Symfony is, I wouldn't hesitate: it's services. Let's find out what a service is and how it's the key to unlocking Symfony's potential.