Applicable in Service-class directives.
This function prepends a header to an HTML file that is sent to the client. The header is specified either as a file name or a URI, thus the header can be dynamically generated.
The following table describes parameters for the add-header function.
Table 5–102 add-header parameters
Parameter |
Description |
---|---|
(Optional) Path name to the file containing the header. Specify either file or uri. By default, the path name is relative. If the path name is absolute, pass the NSIntAbsFilePath parameter as yes. |
|
(Optional) URI pointing to the resource containing the header. Specify either file or uri. |
|
(Optional) If the file parameter is specified, the NSIntAbsFilePath parameter determines whether the file name is absolute or relative. The default is relative. Set the value to yes to indicate an absolute file path. |
|
method |
(Optional) Common to all Service-class functions. |
query |
(Optional) Common to all Service-class functions. |
UseOutputStreamSize |
(Optional) Common to all Service-class functions. |
flushTimer |
(Optional) Common to all Service-class functions. |
ChunkedRequestBufferSize |
(Optional) Common to all Service-class functions. |
ChunkedRequestTimeout |
(Optional) Common to all Service-class functions. |
bucket |
(Optional) Common to all obj.conf functions. |
Service method=GET fn=add-header file="headers/header1.html" Service method=GET fn=add-footer file="D:/Sun/Server61/server1/headers/header1.html" NSIntAbsFilePath="yes" |