First, you can use <Perl> sections to configure Apache. But I believe you can only do this in the httpd.conf & PerlRequire files. <Perl> sections are very cool, but from what I've seen to have some bugs you might have to work around. I've never used them personally, but many folks do. They work well, and can save lots of tedious work in httpd.conf
To answer your second question, yes, your users can potentially use the mod_perl API to do nasty things. You can read some of the configuration through $r->server->xxx methods. See pg 455 in the Eagle book.
Depending on how much power you grant to .htaccess files, you can do some interesting things in setting PerlHandlers. The major problem is that everything is cached in RAM. And there are ways to get to the stored values.
Bottom line: if you trust the users on the system, go for it. If you're worried about kiddies, you should forgo mod_perl. I hope some of these potential security problems are addressed in mod_perl 2, but I don't know.
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.