security - Using the PHP built-in server in production -


I was recently curious about PHP 5.4's built-in webserver. On the surface it seems that, however, with enough work, it may be possible to distribute PHP applications which are traditionally dependent on a different web server, such as WordPress, the form of standalone scripts In that, you can only php -S localhost: 80 ap.php (or, more likely, '. Wordpress.sh' ). They can also ship from their own PHP interpreter, which requires application for all needs, which will repeat the need to target many different versions of the language.

It is searching the wheel to some extent again, but it certainly reduces the increase in portability and complexity for the end user.

However, I looked at the following:

This web server was designed for application development support. It can also be useful for testing purposes or for applications running in controlled displays. It is not intended to be a full-featured web server, it should not be used on any public network.

This will clearly refer to issues like proper file system security and will serve the correct HTTP headers, which can be worked through it. However, what's more for this? Is there a built-in security concern and / or technical limitations with the built-in web server of PHP, in the production environment that can not be used around? If so, what are they?

I can think of a lot of operational issues, why do not you want

  • Threshing
  • Capability (not tested, but I'm assuming that NGN is faster than PHP's built-in non-optimized server)
  • Whatever you have There is also something, it enhances Enigenx, Apache, and IIS (things like new residues).

    However, there is a solution where you take the most out of running PHP with your web-in web server, while the benefits of running the web server are most of the benefits. That is, you can use a server like NGNX as a reverse proxy on PHP's underlying web server. In this situation, HTTP becomes a replacement for FastcGI, according to the general use of the built-in HTTP server in Node.js applications.

    Now, I can not talk to the special of the warning. As a documentation I am not a PHP writer if it were mine, then I will not run PHP for the next reasons, but I Maybe consider it to run like NGN on the back of the real web server. Although for me, setting up a PHP with PHP-FPM is not difficult, and I guess about the deepest accessibility of the built-in server which is documented only for testing.

  • Comments

    Popular posts from this blog

    php - PDO bindParam() fatal error -

    logging - How can I log both the Request.InputStream and Response.OutputStream traffic in my ASP.NET MVC3 Application for specific Actions? -

    java - Why my included JSP file won't get processed correctly? -