Strictly speaking you won't know the type until it is send; before that any code might still change the response. In any case you don't want to run a bunch of code just to figure out if whether you want to allow the user access.

So, in other words, if you can't figure out the content-type from the url, I would suggest you use a more structured approach and put non-authorization-required content under a seperate path: "http://example.com/public/" and "http://example.com/auth/" for instance, and then you can easily match the uri in the auth phase, or even configure apache to just run the auth handlers for the right content.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

In reply to Re: mod_perl, getting filename or mime type by Joost
in thread mod_perl, getting filename or mime type by pingo

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.