On Wed, Jun 10, 2009 at 11:20 AM, Tomas Doran <[email protected]> wrote:
> > On 10 Jun 2009, at 10:04, Francesc Romà i Frigolé wrote: > >> >> Also, in the static directory I could leave some things public ( css, >> javascript, icons...) but make other private ( uploads, reports, ...) by >> placing a .htaccess file requiring authentication in each corresponding >> directory. >> >> > Why not just totally exclude public things from going into Catalyst at all? Yes, that is what I'm doing, I should have said it more explicitly. I don't make the application root directory ( /public_html/myapp) go through Catalyst. Only the subdirectories that have an explicit .htaccess do. So everything is "static" unless stated otherwise. There is no .htaccess in /public_html/myapp > BTW, auth doesn't have to be configured in .htaccess, in fact, I'd only do > that if you have to, as re-reading htaccess files can end up fairly > expensive. > I'm on a shared hosting. I'm trying to find out if I can get a reasonable performance serving non public static files. With the setup I described there is at most one .htaccess file that needs to be read for each request: either it redirects dynamic stuff to catalyst ( different .htaccess for public or private ) or serves a public static file (no .htaccess to be read) or serves static private files (no catalyst, static/private/.htaccess) cheers
_______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
