Space filtering in URL parameter

Question

PHP

I'm writing my first site and I'm nailing up steel armor in advance every piece of code from the same "curious" people like me.

The thing is: http://site.com/?id=1

and this:

http://site.com/?id=1 _

In the first case, we have an id without a space, the second, on the contrary, with it. Before asking this question, I went through the sites and checked who is doing what in this case.

So, they react negatively to the space and send them to the forest:

- facebook - habrahabr

Ignore

- Google and its projects - Toster, Freelansim

For me, Google and Habr are authoritative in this regard (I think the administration of Habr has been taught by defacement), but oddly enough, the positions diverge.

To be or not to be?

Answer 1

This question has nothing to do with "curiosity". And to think that this is in any way related to SQL is a direct road to injection.

And it has - to data validation and, in part, to usability and SEO.

A space is an irrelevant character, it can be trimmed automatically. So I'll talk about "partially valid" URLs in general. Considering that no one is now typing urls by hand, and search engines may have a bad attitude towards the existence of the same page with different urls - I would not skip it, I would give 404.

Answer 2

$_GET = array_filter($_GET, 'trim');

and no spaces on the sides in all get variables

Answer 3

I am against such spaces, they are not needed

Answer 4

What difference does it make if there is a gap or not?
Whether there is a space in the URL or not, $id will still be a number.

Answer 5

It is more correct to throw an error if such an argument is invalid, or if there is no page with id="1", because there will be no page duplication at different URLs. Also, if it concerns security issues and not SEO, then it is correct to check all input parameters by type and valid values, and use prepared statments and parameter binding when working with the database.