On 1/11/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Surely someone else has run into this problem. > > Run TG behind Apache, with Apache serving up everything from the > /static directory. Problem is, how do you restrict access to /static > files, such that only logged-in users can see them? > > Actually, I'll make the problem more generic. Just say you're running > TG only (no Apache). How then would you restrict access to /static > files? >
If you have static content that needs to be secured by a TG mechanism, then TG must handle the requests for that content. So, in this case, you can let TG handle all of your static content OR separate out /static-public content from /static-secured and let apache handle /static-public like it does now, and TG would handle /static-secured. -Jeff --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
