tye had a really interesting idea he told me via Chatterbox. He said I should try making the script a non-parsed headers script and feed in my own HTTP headers manually. I did so, and now all my HTTP headers appear to be "correct" (i.e. incorrect intentionally).
Problem is, it doesn't appear to work when I try this using CGI.pm, but only as a flat series of lines.
my $cgi = new CGI;
-nph => 1,
-type => 'text/html; charset=ISO-8859-1',
-cache_control => 'private',
-connection => 'close',
-server => 'Microsoft-IIS/6.0'
HTTP/1.1 200 OK
Date: Mon, 14 Oct 2002 21:41:25 GMT
Expires: Mon, 25 Oct 2010 21:21:21 GMT
P3P: CP='ALL IND DSP COR ADM CONo CUR CUSo IVAo IVDo PSA PSD TAI TELo
+OUR SAMo CNT COM INT NAV ONL PHY PRE PUR UNI'
<HTML><HEAD><!-- the rest of the html document -->
The problem is that NetCraft is still reporting me running Apache. However, after some reading on their site, I get the feeling (backed by no real evidence) that they query for new site data on a daily basis. So perhaps by tomorrow, my problems will be solved.
code('Perl') || die;
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.