> Review: .txt --> no processing or restriction > .htm? --> processing and restriction via the normal expectations > apache index > control --> adheres to the EMBPERL_URIMATCH, but not EMBPERL_ALLOW > > Perhaps that helps.
I was wrong, setting EMBPERL_ALLOW (\.htm.?|\.epl$) in the 'root' block (ie the file) also restricts my access to .txt files. Sorry about that. This means it acts just like the apache index control (a REQUEST to the http://host/eptest directory). My guess is that Embperl::Object completely controls the directory, and EMBPERL_ALLOW restricts the module from using things *before* it can determine what to do with a requested component (ie should it not process and just serve the .txt file). The EMBPERL_URIMATCH then works in both of these cases once EMBPERL_ALLOW is removed, as it has been 'allowed' to view them, then chooses not to process them. Sound right? Cameron --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]