 |
|
|
PipeBoost Custom CGI Directives Some of the PipeBoost features can be controlled from CGI scripts like ASP, ASPX, Perl script,
CFML or PHP or from ISAPI applications. This is accomplished by supplying HTTP response header fields (see
HTTP RFC; Internet RFCs; RFC# 2616).
In addition to some standard fields, like Cache-Control, custom header
fields (directives) can be used. PipeBoost may also supply its own request
header fields to pass information to scripts and applications along with
the request. This provides simple but efficient means of bidirectional
communication between PipeBoost and web applications.
Directives
| X-Pb-CompressionLevel
|
controls whether the
output of a script is compressed and sets the compression level |
| X-Pb-CacheOn |
controls whether
caching is enabled for a script, if possible |
| X-Pb-DeleteCache |
instructs PipeBoost to
delete all cached copies of the specified file or files |
| X-Pb-Flush |
controls when the
PipeBoost compression buffer is flushed to a client |
| X-Pb-SendCache |
controls the sending of
cached copies of a page |
| X-Pb-CacheDate |
provides the date and
time of a cached page, if cache pre-validation succeeded |
| X-Pb-CacheValid
|
provides the result of
cache pre-validation, if it took place |
Syntax
Response fields
In ASP:
Response.AddHeader "directive-name", "value"
In Perl:
print "directive-name: value\n";
Request fields
In ASP:
value = Request.ServerVariables("HTTP_directive_name")
In Perl:
value = $ENV{'HTTP_directive_name'};
See the actual directives in PipeBoost Help for explanation of parameters.
Notes
When PipeBoost ISAPI filter encounters one of these custom response
header directives, it will read, process and remove it from the actual
client stream.
|
|
