Fossil SCM
Fix typos in the How CGI Works document.
Commit
9c87cb2912c3a1db38ebf260d309bcdda9ba7d76
Parent
e379665aaf92e27…
1 file changed
+5
-5
+5
-5
| --- www/aboutcgi.wiki | ||
| +++ www/aboutcgi.wiki | ||
| @@ -1,9 +1,9 @@ | ||
| 1 | 1 | <title>How CGI Works In Fossil</title> |
| 2 | 2 | <h2>Introduction</h2><blockquote> |
| 3 | 3 | <p>CGI or "Common Gateway Interface" is a venerable yet reliable technique for |
| 4 | -generating dynamic web content. This article give a quick background on how | |
| 4 | +generating dynamic web content. This article gives a quick background on how | |
| 5 | 5 | CGI works and describes how Fossil can act as a CGI service. |
| 6 | 6 | <p>This is a "how it works" guide. If you just want to set up Fossil |
| 7 | 7 | as a CGI server, see the [./server.wiki | Fossil Server Setup] page. |
| 8 | 8 | </blockquote> |
| 9 | 9 | <h2>A Quick Review Of CGI</h2><blockquote> |
| @@ -90,11 +90,11 @@ | ||
| 90 | 90 | <blockquote><pre> |
| 91 | 91 | #!/usr/bin/fossil |
| 92 | 92 | repository: /home/www/repos/project.fossil |
| 93 | 93 | </pre></blockquote> |
| 94 | 94 | The first line of the script is a |
| 95 | -"[https://en.wikipedia.org/wiki/Shebang_%28Unix%29|shebank]" | |
| 95 | +"[https://en.wikipedia.org/wiki/Shebang_%28Unix%29|shebang]" | |
| 96 | 96 | that tells the operating system what program to use as the interpreter |
| 97 | 97 | for this script. On unix, when you execute a script that starts with |
| 98 | 98 | a shebang, the operating system runs the program identified by the |
| 99 | 99 | shebang with a single argument that is the full pathname of the script |
| 100 | 100 | itself. |
| @@ -157,14 +157,14 @@ | ||
| 157 | 157 | directory: /home/www/repos |
| 158 | 158 | </pre></blockquote> |
| 159 | 159 | Suppose the /home/www/repos directory contains files named |
| 160 | 160 | <b>one.fossil</b>, <b>two.fossil</b>, and <b>subdir/three.fossil</b>. |
| 161 | 161 | Further suppose that the name of the CGI script (relative to the root |
| 162 | -of the webservers document area) is "cgis/example2". Then to | |
| 162 | +of the webserver document area) is "cgis/example2". Then to | |
| 163 | 163 | see the timeline for the "three.fossil" repository, the URL would be: |
| 164 | 164 | <blockquote> |
| 165 | -<b>http://yourstuff.com/cgis/example2/subdir/three/timeline</b> | |
| 165 | +<b>http://example.com/cgis/example2/subdir/three/timeline</b> | |
| 166 | 166 | </blockquote> |
| 167 | 167 | Here is what happens: |
| 168 | 168 | <ol> |
| 169 | 169 | <li> The input URI on the HTTP request is |
| 170 | 170 | <b>/cgis/example2/subdir/three/timeline</b> |
| @@ -195,11 +195,11 @@ | ||
| 195 | 195 | parameter that are part of the POST content, and cookies. Each information |
| 196 | 196 | source is seen as a space of key/value pairs which are loaded into an |
| 197 | 197 | internal property hash table. The code that runs to generate the reply |
| 198 | 198 | can then reference various properties values. |
| 199 | 199 | Fossil does not care where the value of each property comes from (POST |
| 200 | -content, cookies, or query parameters) only that the property exist | |
| 200 | +content, cookies, or query parameters) only that the property exists | |
| 201 | 201 | and has a value. |
| 202 | 202 | <li><p> |
| 203 | 203 | The "[/help?cmd=ui|fossil ui]" and "[/help?cmd=server|fossil server]" commands |
| 204 | 204 | are implemented using a simple built-in web server that accepts incoming HTTP |
| 205 | 205 | requests, translates each request into a CGI invocation, then creates a |
| 206 | 206 |
| --- www/aboutcgi.wiki | |
| +++ www/aboutcgi.wiki | |
| @@ -1,9 +1,9 @@ | |
| 1 | <title>How CGI Works In Fossil</title> |
| 2 | <h2>Introduction</h2><blockquote> |
| 3 | <p>CGI or "Common Gateway Interface" is a venerable yet reliable technique for |
| 4 | generating dynamic web content. This article give a quick background on how |
| 5 | CGI works and describes how Fossil can act as a CGI service. |
| 6 | <p>This is a "how it works" guide. If you just want to set up Fossil |
| 7 | as a CGI server, see the [./server.wiki | Fossil Server Setup] page. |
| 8 | </blockquote> |
| 9 | <h2>A Quick Review Of CGI</h2><blockquote> |
| @@ -90,11 +90,11 @@ | |
| 90 | <blockquote><pre> |
| 91 | #!/usr/bin/fossil |
| 92 | repository: /home/www/repos/project.fossil |
| 93 | </pre></blockquote> |
| 94 | The first line of the script is a |
| 95 | "[https://en.wikipedia.org/wiki/Shebang_%28Unix%29|shebank]" |
| 96 | that tells the operating system what program to use as the interpreter |
| 97 | for this script. On unix, when you execute a script that starts with |
| 98 | a shebang, the operating system runs the program identified by the |
| 99 | shebang with a single argument that is the full pathname of the script |
| 100 | itself. |
| @@ -157,14 +157,14 @@ | |
| 157 | directory: /home/www/repos |
| 158 | </pre></blockquote> |
| 159 | Suppose the /home/www/repos directory contains files named |
| 160 | <b>one.fossil</b>, <b>two.fossil</b>, and <b>subdir/three.fossil</b>. |
| 161 | Further suppose that the name of the CGI script (relative to the root |
| 162 | of the webservers document area) is "cgis/example2". Then to |
| 163 | see the timeline for the "three.fossil" repository, the URL would be: |
| 164 | <blockquote> |
| 165 | <b>http://yourstuff.com/cgis/example2/subdir/three/timeline</b> |
| 166 | </blockquote> |
| 167 | Here is what happens: |
| 168 | <ol> |
| 169 | <li> The input URI on the HTTP request is |
| 170 | <b>/cgis/example2/subdir/three/timeline</b> |
| @@ -195,11 +195,11 @@ | |
| 195 | parameter that are part of the POST content, and cookies. Each information |
| 196 | source is seen as a space of key/value pairs which are loaded into an |
| 197 | internal property hash table. The code that runs to generate the reply |
| 198 | can then reference various properties values. |
| 199 | Fossil does not care where the value of each property comes from (POST |
| 200 | content, cookies, or query parameters) only that the property exist |
| 201 | and has a value. |
| 202 | <li><p> |
| 203 | The "[/help?cmd=ui|fossil ui]" and "[/help?cmd=server|fossil server]" commands |
| 204 | are implemented using a simple built-in web server that accepts incoming HTTP |
| 205 | requests, translates each request into a CGI invocation, then creates a |
| 206 |
| --- www/aboutcgi.wiki | |
| +++ www/aboutcgi.wiki | |
| @@ -1,9 +1,9 @@ | |
| 1 | <title>How CGI Works In Fossil</title> |
| 2 | <h2>Introduction</h2><blockquote> |
| 3 | <p>CGI or "Common Gateway Interface" is a venerable yet reliable technique for |
| 4 | generating dynamic web content. This article gives a quick background on how |
| 5 | CGI works and describes how Fossil can act as a CGI service. |
| 6 | <p>This is a "how it works" guide. If you just want to set up Fossil |
| 7 | as a CGI server, see the [./server.wiki | Fossil Server Setup] page. |
| 8 | </blockquote> |
| 9 | <h2>A Quick Review Of CGI</h2><blockquote> |
| @@ -90,11 +90,11 @@ | |
| 90 | <blockquote><pre> |
| 91 | #!/usr/bin/fossil |
| 92 | repository: /home/www/repos/project.fossil |
| 93 | </pre></blockquote> |
| 94 | The first line of the script is a |
| 95 | "[https://en.wikipedia.org/wiki/Shebang_%28Unix%29|shebang]" |
| 96 | that tells the operating system what program to use as the interpreter |
| 97 | for this script. On unix, when you execute a script that starts with |
| 98 | a shebang, the operating system runs the program identified by the |
| 99 | shebang with a single argument that is the full pathname of the script |
| 100 | itself. |
| @@ -157,14 +157,14 @@ | |
| 157 | directory: /home/www/repos |
| 158 | </pre></blockquote> |
| 159 | Suppose the /home/www/repos directory contains files named |
| 160 | <b>one.fossil</b>, <b>two.fossil</b>, and <b>subdir/three.fossil</b>. |
| 161 | Further suppose that the name of the CGI script (relative to the root |
| 162 | of the webserver document area) is "cgis/example2". Then to |
| 163 | see the timeline for the "three.fossil" repository, the URL would be: |
| 164 | <blockquote> |
| 165 | <b>http://example.com/cgis/example2/subdir/three/timeline</b> |
| 166 | </blockquote> |
| 167 | Here is what happens: |
| 168 | <ol> |
| 169 | <li> The input URI on the HTTP request is |
| 170 | <b>/cgis/example2/subdir/three/timeline</b> |
| @@ -195,11 +195,11 @@ | |
| 195 | parameter that are part of the POST content, and cookies. Each information |
| 196 | source is seen as a space of key/value pairs which are loaded into an |
| 197 | internal property hash table. The code that runs to generate the reply |
| 198 | can then reference various properties values. |
| 199 | Fossil does not care where the value of each property comes from (POST |
| 200 | content, cookies, or query parameters) only that the property exists |
| 201 | and has a value. |
| 202 | <li><p> |
| 203 | The "[/help?cmd=ui|fossil ui]" and "[/help?cmd=server|fossil server]" commands |
| 204 | are implemented using a simple built-in web server that accepts incoming HTTP |
| 205 | requests, translates each request into a CGI invocation, then creates a |
| 206 |