Common Gateway Interface: Difference between revisions
Jump to navigation
Jump to search
imported>Annh07 Reverted 1 edit by Muhammad047 (talk): Not grammar |
imported>LightandDark2000 m Reverted edit by ~2025-37592-26 (talk) to last version by SuperFastSpellChecker |
||
| Line 9: | Line 9: | ||
Such programs are often written in a [[scripting language]] and are commonly referred to as ''CGI scripts'', but they may include [[compiler|compiled]] programs.{{ref RFC|3875|section=1.4}} | Such programs are often written in a [[scripting language]] and are commonly referred to as ''CGI scripts'', but they may include [[compiler|compiled]] programs.{{ref RFC|3875|section=1.4}} | ||
A typical use case occurs when a web user submits a [[web form]] on a web page that uses CGI. The form's data is sent to the web server within | A typical use case occurs when a web user submits a [[web form]] on a web page that uses CGI. The form's data is sent to the web server within an [[HTTP request]] with a [[URL]] denoting a CGI script. The web server then launches the CGI script in a new [[computer process]], passing the form data to it. The CGI script passes its output, usually in the form of [[HTML]], to the Web server, and the server relays it back to the browser as its [[HTTP response|response]] to the browser's request.{{ref RFC|3875}} | ||
Developed in the early 1990s, CGI was the earliest common method available that allowed a web page to be interactive. Due to a necessity to run CGI scripts in a separate process every time the request comes in from a client, various alternatives were developed. | Developed in the early 1990s, CGI was the earliest common method available that allowed a web page to be interactive. Due to a necessity to run CGI scripts in a separate process every time the request comes in from a client, various alternatives were developed. | ||