Скачать или смотреть How to Execute PHP in Specific HTML Files on NGINX

Learn how to efficiently execute `PHP` code only in selected HTML files when using `NGINX`, ensuring that static HTML files remain untouched.
---
This video is based on the question https://stackoverflow.com/q/66529993/ asked by the user 'Pelin' ( https://stackoverflow.com/u/9038829/ ) and on the answer https://stackoverflow.com/a/66533830/ provided by the user 'Danila Vershinin' ( https://stackoverflow.com/u/285069/ ) 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 execute PHP on Specific HTML Files on NGINX

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.
---
Executing PHP Code in Specific HTML Files on NGINX

If you've ever tried to run PHP code inside HTML files, you know that it can lead to problems if not handled correctly. In NGINX, by default, all HTML files may be processed through the PHP engine, which can cause static HTML files to function incorrectly. This guide will guide you through the solution to ensure that only specific HTML files execute PHP code, while keeping others as pure HTML.

The Problem Explained

When working with NGINX, you may want certain HTML files to include PHP code, while achieving the opposite for others. An incorrect configuration could mean that all your HTML files will be processed by the PHP engine, leading to unexpected behavior and issues with static files.

Here's What You Have Already Tried

You attempted to utilize an .htaccess file as a potential solution. Unfortunately, this approach won’t work with NGINX since that server type does not support .htaccess configurations—it's a feature mainly associated with Apache.

Your current NGINX configuration looks something like this:

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

While this code works perfectly in serving PHP files, it also processes all of your HTML files through PHP, which is not what you desire.

The Solution

The key to solving this issue lies in creating specific location directives that target only the HTML files where you want to execute PHP. Below, we’ll break down the steps you need to take to implement this solution effectively.

Step 1: Use Exact Matching

Instead of applying a general rule to all HTML files, you'll set up an exact match for each HTML file that should process PHP. Here’s how you can configure it:

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

Breakdown of the Configuration

location = /mypage.html: This line specifies that this configuration will only apply to the /mypage.html file. The equal sign = denotes an exact match.

fastcgi_pass: This tells NGINX to use the PHP processor defined, which in this case is linked to the PHP FastCGI Process Manager (FPM).

include nginxconfig.io/php_fastcgi.conf: This line includes the appropriate configuration file to help handle the FastCGI requests properly.

Step 2: Repeat for Other Specified HTML Files (If Necessary)

If you have more HTML files that you want to execute PHP code within, you can simply duplicate the location block for each file, adjusting the filename accordingly.

For example:

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

Step 3: Test Your Configuration

After making these changes, remember to test your NGINX configuration to ensure there are no syntax errors:

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

If everything checks out, proceed to reload the NGINX server:

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

Conclusion

By utilizing exact matching in your NGINX configuration, you can run PHP code only on designated HTML files. This approach not only streamlines the server's performance but also keeps your static files functioning as intended. If you encounter any issues or have further questions about configuring NGINX, feel free to reach out!

With these steps, you should now be adroitly managing PHP execution within specific HTML files without cluttering your server's efficiency.