If I were you I would check the error logs. I would also
suggest adding more informative dies, and paying attention
to security. For instance look at
perlsec, turn on
taint checking, and stop trusting that user-supplied
filenames will be clean.
Here is a simple working example I did a while
ago which just echoes the file back to the browser. For
more information on some of the security issues that need
to be addressed, you may wish to visit the
WWW
Security FAQ including this section on
CGI scripts.
Or you can just wander by some samples of how people
actually crack
scripts. (Hint, it is your vulnerability to some of these
cracks that made me sit down and write this. I leave it to
you to figure out which ones...)
For a random past discussion on this (which explains both
why you cannot safely ignore these attacks and gives some
pointers on how to protect yourself) take a look at
Warning our Fellow Monks.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.