With PHP, if you want to make a resource visible only to some users, you put in a folder outside of what is shared by Apache but where PHP has read access. Then when the user tries of read it, if they are allowed, you open it with PHP's readfile() function. For Lift, what is the equivalent. The Siteman seems to allow any non-HTML file to be read. Can I make the Sitemap block images in a specific location for some users and not others?
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code
With PHP, if you want to make a resource visible only to some users, you put in a folder outside of what is shared by Apache but where PHP has read access. Then when the user tries of read it, if they are allowed, you open it with PHP's readfile() function. For Lift, what is the equivalent. The Siteman seems to allow any non-HTML file to be read. Can I make the Sitemap block images in a specific location for some users and not others?
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code
If the file is something static and is part of the application (replaced
only when the application is updated) and you are deploying to a
standard JEE container, you can put the file inside WEB-INF folder
structure. By definition WEB-INF is never served by the web server, only
accessible by code from the application
LiftRules.defaultGetResource search classpath resources, then try the
standard ServletContext.getResource(). I think I would add the file to
WEB-INF, and use LiftRules.dispatch to make the file available to the
user after validation