Fossil SCM
[Grammar] aboutcgi.wiki corrections
Commit
d4a21cd45f4a2e2eaa650ad7f3c445e25edbe23c3560cca48dccf68d55f3c017
Parent
073e0b6bdbf18e6…
1 file changed
+5
-5
+5
-5
| --- www/aboutcgi.wiki | ||
| +++ www/aboutcgi.wiki | ||
| @@ -8,30 +8,30 @@ | ||
| 8 | 8 | |
| 9 | 9 | This is a "how it works" guide. This document provides background |
| 10 | 10 | information on the CGI protocol so that you can better understand what |
| 11 | 11 | is going on behind the scenes. If you just want to set up Fossil |
| 12 | 12 | as a CGI server, see the [./server/ | Fossil Server Setup] page. Or |
| 13 | -if you want to development CGI-based extensions to Fossil, see | |
| 14 | -the [./serverext.wiki|CGI Server Extensions] page. | |
| 13 | +if you want to develop CGI-based extensions to Fossil, see the | |
| 14 | +[./serverext.wiki|CGI Server Extensions] page. | |
| 15 | 15 | |
| 16 | 16 | <h2>A Quick Review Of CGI</h2> |
| 17 | 17 | |
| 18 | 18 | An HTTP request is a block of text that is sent by a client application |
| 19 | 19 | (usually a web browser) and arrives at the web server over a network |
| 20 | 20 | connection. The HTTP request contains a URL that describes the information |
| 21 | 21 | being requested. The URL in the HTTP request is typically the same URL |
| 22 | 22 | that appears in the URL bar at the top of the web browser that is making |
| 23 | -the request. The URL might contain a "?" character followed | |
| 23 | +the request. The URL might contain a "?" character followed by | |
| 24 | 24 | query parameters. The HTTP will usually also contain other information |
| 25 | 25 | such as the name of the application that made the request, whether or |
| 26 | 26 | not the requesting application can accept a compressed reply, POST |
| 27 | 27 | parameters from forms, and so forth. |
| 28 | 28 | |
| 29 | 29 | The job of the web server is to interpret the HTTP request and formulate |
| 30 | 30 | an appropriate reply. |
| 31 | -The web server is free to interpret the HTTP request in any way it wants. | |
| 32 | -But most web servers follow a similar pattern, described below. | |
| 31 | +The web server is free to interpret the HTTP request in any way it wants, | |
| 32 | +but most web servers follow a similar pattern, described below. | |
| 33 | 33 | (Note: details may vary from one web server to another.) |
| 34 | 34 | |
| 35 | 35 | Suppose the filename component of the URL in the HTTP request looks like this: |
| 36 | 36 | |
| 37 | 37 | <pre>/one/two/timeline/four</pre> |
| 38 | 38 |
| --- www/aboutcgi.wiki | |
| +++ www/aboutcgi.wiki | |
| @@ -8,30 +8,30 @@ | |
| 8 | |
| 9 | This is a "how it works" guide. This document provides background |
| 10 | information on the CGI protocol so that you can better understand what |
| 11 | is going on behind the scenes. If you just want to set up Fossil |
| 12 | as a CGI server, see the [./server/ | Fossil Server Setup] page. Or |
| 13 | if you want to development CGI-based extensions to Fossil, see |
| 14 | the [./serverext.wiki|CGI Server Extensions] page. |
| 15 | |
| 16 | <h2>A Quick Review Of CGI</h2> |
| 17 | |
| 18 | An HTTP request is a block of text that is sent by a client application |
| 19 | (usually a web browser) and arrives at the web server over a network |
| 20 | connection. The HTTP request contains a URL that describes the information |
| 21 | being requested. The URL in the HTTP request is typically the same URL |
| 22 | that appears in the URL bar at the top of the web browser that is making |
| 23 | the request. The URL might contain a "?" character followed |
| 24 | query parameters. The HTTP will usually also contain other information |
| 25 | such as the name of the application that made the request, whether or |
| 26 | not the requesting application can accept a compressed reply, POST |
| 27 | parameters from forms, and so forth. |
| 28 | |
| 29 | The job of the web server is to interpret the HTTP request and formulate |
| 30 | an appropriate reply. |
| 31 | The web server is free to interpret the HTTP request in any way it wants. |
| 32 | But most web servers follow a similar pattern, described below. |
| 33 | (Note: details may vary from one web server to another.) |
| 34 | |
| 35 | Suppose the filename component of the URL in the HTTP request looks like this: |
| 36 | |
| 37 | <pre>/one/two/timeline/four</pre> |
| 38 |
| --- www/aboutcgi.wiki | |
| +++ www/aboutcgi.wiki | |
| @@ -8,30 +8,30 @@ | |
| 8 | |
| 9 | This is a "how it works" guide. This document provides background |
| 10 | information on the CGI protocol so that you can better understand what |
| 11 | is going on behind the scenes. If you just want to set up Fossil |
| 12 | as a CGI server, see the [./server/ | Fossil Server Setup] page. Or |
| 13 | if you want to develop CGI-based extensions to Fossil, see the |
| 14 | [./serverext.wiki|CGI Server Extensions] page. |
| 15 | |
| 16 | <h2>A Quick Review Of CGI</h2> |
| 17 | |
| 18 | An HTTP request is a block of text that is sent by a client application |
| 19 | (usually a web browser) and arrives at the web server over a network |
| 20 | connection. The HTTP request contains a URL that describes the information |
| 21 | being requested. The URL in the HTTP request is typically the same URL |
| 22 | that appears in the URL bar at the top of the web browser that is making |
| 23 | the request. The URL might contain a "?" character followed by |
| 24 | query parameters. The HTTP will usually also contain other information |
| 25 | such as the name of the application that made the request, whether or |
| 26 | not the requesting application can accept a compressed reply, POST |
| 27 | parameters from forms, and so forth. |
| 28 | |
| 29 | The job of the web server is to interpret the HTTP request and formulate |
| 30 | an appropriate reply. |
| 31 | The web server is free to interpret the HTTP request in any way it wants, |
| 32 | but most web servers follow a similar pattern, described below. |
| 33 | (Note: details may vary from one web server to another.) |
| 34 | |
| 35 | Suppose the filename component of the URL in the HTTP request looks like this: |
| 36 | |
| 37 | <pre>/one/two/timeline/four</pre> |
| 38 |