Home / Questions / 350313
Accepted
Miguel
Asked: 2020-04-29 04:38:40 +0800 CST 2020-04-29 04:38:40 +0800 CST

Change URLs with parameters to "friendly URLs"

  • 772

I have developed a website with PHP, MySQL, CSS, Javascript and HTML. The problem that I find is that when you make the pages dynamic, the URLs are usually like this:

/tests.php?ID=2
/panel.php?ID=7&GENERO=2
/specifies.php?ID=326&GENERO=2&CATEGORY=7

And of course, all this does not like google very much.

I wanted to know if it is possible to remove the extensions .phpand create friendly urls.

I use an NGINX server .

My .conf file that loads the web:

server {
 listen 8360;
 listen [::]:8360;

 root /var/www/laboratorio/;

 # Add index.php to the list if you are using PHP
 index index.html index.htm index.nginx-debian.html index.php;

 server_name 82.223.13.57;

 location ~* \.(jpg|jpeg|png|gif|ico|svg)$ { expires 365d; } location ~* \.(css|js|pdf)$ { expires 30d; }

 location ~ ^/.well-known {
    allow all;
 }

 location / {
 # First attempt to serve request as file, then
 # as directory, then fall back to displaying a 404.
 try_files $uri $uri/ =404;
 error_page 405 = $uri;
 }

 # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
 #
 location ~ \.php$ {
 include snippets/fastcgi-php.conf;

 fastcgi_pass unix:/run/php/php7.2-fpm.sock;
 }

 # deny access to .htaccess files, if Apache's document root
 # concurs with nginx's one
 location ~ /\.ht {
  deny all;
 }
}
php

1 Answers

  1. Best Answer

    There are many frameworks that use "friendly URLs" and on their websites they show the typical configuration for this type of scenario.

    To begin with, you should create a single input PHP file that we will call "router". It will be the script in charge of collecting all the HTTP requests and calling the appropriate PHP based on the parameters given to it.

    In Slim, for example, the instructions for "rewriting" the URLs are here :

    server {
    listen ...; server_name ...; root ...;

    # Esto es lo más importante:
    try_files $uri /index.php;

    location /index.php {
        fastcgi_connect_timeout 3s;     # default of 60s is just too long
        fastcgi_read_timeout 10s;       # default of 60s is just too long
        include fastcgi_params;
        fastcgi_pass 127.0.0.1:9000;    # assumes you are running php-fpm locally on port 9000
    }
}

    The "magic" is created on this line:

    try_files $uri /index.php;

    It first tries, if it exists, to load the CSS, JS or image file from the file system. If it does not exist, it passes the request to the router ( index.php).

    Also, you can create a unique file rule for PHP as suggested in the configuration file (instead of file pattern ending in .php):

    location /index.php { ... }

    Your router will receive the request with the URL in $_SERVER['REQUEST_URI']. You need to parse that variable for which PHP to run and what parameters to pass to it.

    Edition:

    With the additional data provided in the question I can suggest the following modifications:

    Capturing requests

    You have two options to get it.

    Using try_files:

    location / {
 # First attempt to serve request as file, then
 # as directory, then fall back to displaying a 404.
 # Si quieres permitir parámetros GET fuera del control del enrutador:
 try_files $uri $uri/ /enrutador.php$is_args$args;
 error_page 405 = $uri;
 }

    Using error_page:

    error_page  404 /enrutador.php;

    request router

    To maximize compatibility with your existing application you should create a script as an entry point to the rest of your PHP scripts, modifying the parameters GETaccording to the content of the URL.

    File example enrutador.php:

    <?php
// Comprobamos el patrón /pruebas/id-descripción
if (preg_match('#^/pruebas/([0-9]+)(-.*)?$#', $_SERVER['REQUEST_URI'], $parametros) === 1) {
  $_GET['ID'] = $parametros[1];
  require_once 'pruebas.php';
  exit;
}

// Comprobamos el patrón /panel/id/genero-descripción
if (preg_match('#^/panel/([0-9]+)/([0-9]+)(-.*)?$#', $_SERVER['REQUEST_URI'], $parametros) === 1) {
  $_GET['ID'] = $parametros[1];
  $_GET['GENERO'] = $parametros[2];
  require_once 'panel.php';
  exit;
}

// Comprobamos el patrón /especifica/id/genero/categoria-descripción
if (preg_match('#^/especifica/([0-9]+)/([0-9]+)/([0-9]+)(-.*)?$#', $_SERVER['REQUEST_URI'], $parametros) === 1) {
  $_GET['ID'] = $parametros[1];
  $_GET['GENERO'] = $parametros[2];
  $_GET['CATEGORIA'] = $parametros[3];
  require_once 'especifica.php';
  exit;
}

// Enviamos un código de error HTTP 404 (página no encontrada)
header("HTTP/1.0 404 Not Found");
die('Página no encontrada');

    Examples of supported URLs

    Here are examples of your URLs compared to those supported by the router:

    • /tests.php?ID=2
    • /tests/2
    • /proofs/2-the-flaming-colossus
    • /panel.php?ID=7&GENDER=2
    • /panel/7/2
    • /panel/7/2-gone-with-the-wind
    • /specify.php?ID=326&GENDER=2&CATEGORY=7
    • /panel/7/2/7
    • /panel/7/2/7-ponyo-on-the-cliff

    As you can see, the descriptions can be arbitrary and they are the ones that will help the search engine to understand the content of your URLs.

    • 2