Fossil SCM
serverext.wiki: added a note about the need to unset GATEWAY_INTERFACE before trying to recursively call the fossil binary.
Commit
e3fbbdc1d05b840d74ef1559419cb274471d3c6d967c8b1bb98271be741ca134
Parent
1cff8d318232ecf…
1 file changed
+13
+13
| --- www/serverext.wiki | ||
| +++ www/serverext.wiki | ||
| @@ -211,10 +211,11 @@ | ||
| 211 | 211 | <h3>3.1 Input Content</h3> |
| 212 | 212 | |
| 213 | 213 | If the HTTP request includes content (for example if this is a POST request) |
| 214 | 214 | then the CONTENT_LENGTH value will be positive and the data for the content |
| 215 | 215 | will be readable on standard input. |
| 216 | + | |
| 216 | 217 | |
| 217 | 218 | <h2>4.0 CGI Outputs</h2> |
| 218 | 219 | |
| 219 | 220 | CGI programs construct a reply by writing to standard output. The first |
| 220 | 221 | few lines of output are parameters intended for the web server that invoked |
| @@ -256,10 +257,22 @@ | ||
| 256 | 257 | "data-title" attribute. |
| 257 | 258 | |
| 258 | 259 | Except for the three cases noted above, Fossil makes no changes or |
| 259 | 260 | additions to the CGI-generated content. Fossil just passes the verbatim |
| 260 | 261 | content back up the stack towards the requester. |
| 262 | + | |
| 263 | +<h3>4.1 <tt>GATEWAY_INTERFACE</tt> and Recursive Calls to fossil</h3> | |
| 264 | + | |
| 265 | +Like many CGI-aware applications, if fossil sees the environment | |
| 266 | +variable <tt>GATEWAY_INTERFACE</tt> when it starts up, it assumes it | |
| 267 | +is running in a CGI environment and behaves differently than when it | |
| 268 | +is run in a non-CGI interactive session. If you intend to run fossil | |
| 269 | +itself from within an extension CGI script, e.g. to run a query | |
| 270 | +against the repository or simply fetch the fossil binary version, make | |
| 271 | +sure to <em>unset</em> the <tt>GATEWAY_INTERFACE</tt> environment | |
| 272 | +variable before doing so, otherwise the invocation will behave as if | |
| 273 | +it's being run in CGI mode. | |
| 261 | 274 | |
| 262 | 275 | <h2>5.0 Filename Restrictions</h2> |
| 263 | 276 | |
| 264 | 277 | For security reasons, Fossil places restrictions on the names of files |
| 265 | 278 | in the extroot directory that can participate in the extension CGI |
| 266 | 279 |
| --- www/serverext.wiki | |
| +++ www/serverext.wiki | |
| @@ -211,10 +211,11 @@ | |
| 211 | <h3>3.1 Input Content</h3> |
| 212 | |
| 213 | If the HTTP request includes content (for example if this is a POST request) |
| 214 | then the CONTENT_LENGTH value will be positive and the data for the content |
| 215 | will be readable on standard input. |
| 216 | |
| 217 | <h2>4.0 CGI Outputs</h2> |
| 218 | |
| 219 | CGI programs construct a reply by writing to standard output. The first |
| 220 | few lines of output are parameters intended for the web server that invoked |
| @@ -256,10 +257,22 @@ | |
| 256 | "data-title" attribute. |
| 257 | |
| 258 | Except for the three cases noted above, Fossil makes no changes or |
| 259 | additions to the CGI-generated content. Fossil just passes the verbatim |
| 260 | content back up the stack towards the requester. |
| 261 | |
| 262 | <h2>5.0 Filename Restrictions</h2> |
| 263 | |
| 264 | For security reasons, Fossil places restrictions on the names of files |
| 265 | in the extroot directory that can participate in the extension CGI |
| 266 |
| --- www/serverext.wiki | |
| +++ www/serverext.wiki | |
| @@ -211,10 +211,11 @@ | |
| 211 | <h3>3.1 Input Content</h3> |
| 212 | |
| 213 | If the HTTP request includes content (for example if this is a POST request) |
| 214 | then the CONTENT_LENGTH value will be positive and the data for the content |
| 215 | will be readable on standard input. |
| 216 | |
| 217 | |
| 218 | <h2>4.0 CGI Outputs</h2> |
| 219 | |
| 220 | CGI programs construct a reply by writing to standard output. The first |
| 221 | few lines of output are parameters intended for the web server that invoked |
| @@ -256,10 +257,22 @@ | |
| 257 | "data-title" attribute. |
| 258 | |
| 259 | Except for the three cases noted above, Fossil makes no changes or |
| 260 | additions to the CGI-generated content. Fossil just passes the verbatim |
| 261 | content back up the stack towards the requester. |
| 262 | |
| 263 | <h3>4.1 <tt>GATEWAY_INTERFACE</tt> and Recursive Calls to fossil</h3> |
| 264 | |
| 265 | Like many CGI-aware applications, if fossil sees the environment |
| 266 | variable <tt>GATEWAY_INTERFACE</tt> when it starts up, it assumes it |
| 267 | is running in a CGI environment and behaves differently than when it |
| 268 | is run in a non-CGI interactive session. If you intend to run fossil |
| 269 | itself from within an extension CGI script, e.g. to run a query |
| 270 | against the repository or simply fetch the fossil binary version, make |
| 271 | sure to <em>unset</em> the <tt>GATEWAY_INTERFACE</tt> environment |
| 272 | variable before doing so, otherwise the invocation will behave as if |
| 273 | it's being run in CGI mode. |
| 274 | |
| 275 | <h2>5.0 Filename Restrictions</h2> |
| 276 | |
| 277 | For security reasons, Fossil places restrictions on the names of files |
| 278 | in the extroot directory that can participate in the extension CGI |
| 279 |