[Catalyst] Serving server-dependent static content

[mreece at vinq.com]

> On 8/12/07, Peter Lytle <pete at bluecampaigns.com> wrote:
>> If someone has a  solution from the Apache side, that's fine but I
>> suspect that it might be
>> easier  to do this with Catalyst::Plugin::Static::Simple
>
> Don't serve static content through perl.  Let your webserver do it.
> Usually people just set up virtual hosts with different
> DOCUMENT_ROOTs.  Is there a reason that won't work for you?
>
> - Perrin

a lot of times, 'static' content is found via database queries.  and
sometimes that content needs to be protected from unauthorized viewers,
and your authorization mechanisms are already built into your application,
so you can't just use Alias/Rewrite directives to still have apache serve
up that tree.

that said, is there a way to have catalyst defer back to the web server,
after deciding not to issue a 403?  has anyone experimented with using
$c->res->status(-1) for this purpose?