是CGI死了吗？ [英] Is cgi dead?

问题描述

好吧，让我们把它放在一个更温和：是CGI（通用网关接口）的遗产

Ok, let's put it in a more mildly: Is cgi (common gateway interface) legacy?

是吗？不是吗？

在什么情况下一个项目今天开始（一个没有NOOT必须与遗留系统或库进行交互）使用CGI？

Under what circumstances would a project starting today (one that does noot have to interact with legacy systems or libraries) use cgi?

推荐答案

这是离死不远了实际。尽管开销，许多虚拟的网络托管公司正在运行PHP，CGI出于安全的考虑，因为它可以suEXEC的使用。 suEXEC的意味着你的脚本在你实际的Unix用户权限执行，因此操作系统的特权分离受到限制。这是一个的多的更强大的安全性比PHP特定open_basedir的替代模式。

It's far from dead actually. Despite the overheads, many virtual web hosting companies are now running PHP as CGI for security considerations, because it can be used with suEXEC. suEXEC means that your scripts execute under your actual Unix user privileges, and thus are restricted by the operating system's privilege separation. This is a much more robust security model than the PHP-specific open_basedir alternative.

此外，CGI是的真正的简单，非常通用的接口，支持它永远不会从Web服务器外出。喜欢的FastCGI和SCGI许多新接口继承CGI通过HTTP标头和其他变量到Web应用程序和回来的路上。即使是PHP的SAPI模仿这与它的 $ _ SERVER 变量。所以CGI不会消失，它只是被建立在这个基础。

Also, CGI is a really simple and quite versatile interface, support for it is never going out from web servers. Many newer interfaces like FastCGI and SCGI inherit the way that CGI passes HTTP headers and other variables to the web application and back. Even PHP's SAPI mimics this with its $_SERVER variable. So CGI is not going away, it is just being built upon.

这篇关于是CGI死了吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！