| 12 | | supported by Cherokee for a long time. At first you might think it is |
|---|
| 13 | | no big deal, but think again. |
|---|
| 14 | | |
|---|
| 15 | | It can be enabled in any CGI, FastCGI or SCGI backend. Basicaly its |
|---|
| 16 | | job is to instruct the web server to ignore the content of the |
|---|
| 17 | | response and replace it by whatever is specified in the header. The |
|---|
| 18 | | main advantage of this is that it will be Cherokee the one serving the |
|---|
| 19 | | file, making use of all its optimizations. It is useful for processing |
|---|
| 20 | | script-output of e.g. php, perl, ruby or any cgi. |
|---|
| | 12 | supported by Cherokee for a while. At first you might think it is no |
|---|
| | 13 | big deal, but think again.It can be enabled in any CGI, FastCGI or |
|---|
| | 14 | SCGI backend. Basicaly its job is to instruct the web server to ignore |
|---|
| | 15 | the content of the response and replace it by whatever is specified in |
|---|
| | 16 | the header. The main advantage of this is that it will be Cherokee the |
|---|
| | 17 | one serving the file, making use of all its optimizations. It is |
|---|
| | 18 | useful for processing script-output of e.g. php, perl, ruby or any |
|---|
| | 19 | cgi. |
|---|