"Daniel L. Rall" <[EMAIL PROTECTED]> writes:
>
> This sounds like an excellent option, but I think that the ftp and http
> paths should be specified via the same staticcontent.path property (in a
> list).
What is the rationale for this ? The static content path is important to
protect local filesystem resources against exposure, but it would be a pain
if we have to edit a property every time a new external content provider
showed up.
Okay, I can understand that some might want to restrict the external sites
you can access from a template - but cant you do that another way ?
Maybe a property :
allowed_sites=http://www.cnn.com/,ftp://ftp.redhat.com
and to open up all external access :
allowed_sites=
and to deny all external access :
allowed_sites=none
regards,
Gunnar
