The site has a combination of public content, static group content and dynamic private content.
I have a site like this. The scripts that generate dynamic content require an appropriate login cookie, and the data that they use is kept in a folder that is not visible to the web server. No apache authentication is required. Works fine, though it does mean that I have to do downloads via a CGI script, instead of letting the web server handle the details.
I would rather control access to the static group content via htaccess authenticate so that update of the pages does not intermingle with the Perl scripts.
So keep the perl scripts in a separate directory?
I'm still not seeing why you need .htaccess control.
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.