How to Use Paths Instead of GET Variables in PHP with NGINX

Описание: Learn how to configure NGINX to use clean URLs and path-based access instead of traditional GET variables in PHP. This guide includes practical examples and rewrite rules!
---
This video is based on the question https://stackoverflow.com/q/66833314/ asked by the user 'efwefwewf' ( https://stackoverflow.com/u/15437251/ ) and on the answer https://stackoverflow.com/a/66838190/ provided by the user 'Ram Babu' ( https://stackoverflow.com/u/1747111/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: How to use paths instead of GET variables in PHP?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Use Paths Instead of GET Variables in PHP with NGINX

In the realm of web development, it's often necessary to improve the way we manage URLs. Instead of relying on traditional GET variables (like ?id=unique), using cleaner path-based URLs can enhance both readability and user experience. This guide aims to tackle the challenge of rewiring PHP scripts in NGINX to enable this kind of URL handling, allowing you to convert requests like example.com/folders/{dynamic}/blog/unique into seamlessly functioning pages.

The Problem

Imagine you have a PHP file located at {dynamic}/blog/index.php, and you want users to access it through a path that includes a unique identifier, without exposing those GET variables. Users should be able to type a URL such as:

[[See Video to Reveal this Text or Code Snippet]]

and have it function the same way as:

[[See Video to Reveal this Text or Code Snippet]]

However, you also face the limitation of not being able to edit .htaccess files, as you are using NGINX instead of Apache. Adding to this complexity, you need to ensure that certain specific IDs point directly to their physical files instead of redirecting to the index file. For example, the URL:

[[See Video to Reveal this Text or Code Snippet]]

should resolve to the actual file called example.php.

The Solution: NGINX Rewrite Rules

To achieve this URL rewriting, we can use NGINX's powerful location and rewrite directives. Below we will discuss how to configure NGINX to meet your needs using specific rewrite rules.

Step-by-Step Configuration

Open Your NGINX Configuration File:
You'll be editing the nginx configuration file, typically located at /etc/nginx/nginx.conf or the relevant site configuration under /etc/nginx/sites-available/.

Add the Rewrite Rules:
You can add the following rewrite rules inside the server block of your configuration:

[[See Video to Reveal this Text or Code Snippet]]

First Line: This rule directs any request for /blog/example to the actual PHP file example.php.

Second Line: This rule captures any unique ID following the /blog/ path and passes it as a GET variable to index.php.

Testing the Configuration

After making these changes, it's essential to test the functionality. You can simply visit the following URLs in your web browser:

For dynamic ID access:

http://localhost/folders/a/blog/hello should resolve to http://localhost/folders/a/blog/index.php?id=hello.

http://localhost/folders/b/blog/hello should resolve similarly for another dynamic folder.

For static file access:

http://localhost/folders/a/blog/example should directly serve example.php.

This logic should hold true for any specified static files that need direct access.

Additional Notes

For any other specific IDs that require direct file access instead of invoking index.php, you can add more rewrite rules in a similar manner.

Ensure that after any configuration changes, you restart or reload NGINX to apply them:

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

Implementing path-based URL management not only helps to keep your URLs clean but also enhances your user experience. By setting up NGINX with the provided rewrite rules, you've successfully redirected dynamic GET requests to a more intuitive path structure without losing functionality.

Using these techniques, you're well on your way to a more organized and user-friendly website. Happy coding!