1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
<HTML>
<BODY TEXT="#000000" LINK="#0000FF" VLINK="#551A8B" ALINK="#FF0000" BGCOLOR="#FFFFFF">
<H2>LayoutHTTPHeader</H2>
<H3>Description</H3>
<P><B>LayoutHTTPHeader</B> allows you to specify a URI that can
be used to display headers that will be used across all
content. Keep in mind that URI's, while being being regular
content are not documents that are meant to be
displayed on the web.
</p>
<H3>Examples</H3>
<BLOCKQUOTE>
<VirtualHost www.foo.com:80><BR>
LayoutHTTPHeader /fullheader.cgi<BR>
</VirtualHost><BR>
</BLOCKQUOTE>
<BR>A simple perl script example:</BR>
<BLOCKQUOTE>
#!/usr/bin/perl -w <BR>
# Quick script to go straight to CSV<BR>
# Brian Aker (brian@tangent.org)<BR>
use strict;<BR>
<BR>
print "Author: Brian Aker\n";<BR>
print "Content-Type: text/html\n\n";<BR>
<BR>
</BLOCKQUOTE>
<P>
<H3>Known Problems</H3>
By overriding Apache's headers you do risk the chance that
if Apache had something important to say you are going to
miss it. Also, dinking up the HTTP headers can leave you
with pages that do not display.
</BODY>
</HTML>
|
