Are the images user-specific? If not, why not serve them out of a directory which does not permit the index to be shown/browsed?
If yes, you can do the same by mangling the image file names with some user id kind of string. Non-authenticated users will not know that string since your webapp won't render it to them. You can achieve the above with an easy-handler I think, and even just use nginx and get better caching control. You can also use a dispatch route, but I don't quite see the need for it yet, since you're only serving up files.. On Thu, Mar 10, 2011 at 8:05 PM, John Morrison <[email protected]>wrote: > Should have mentioned I have also explored using an on-demand-selector > as a "hidden" pane in my navigation. The Lisp on-demand dispatch > function is called as a result of the request, seemingly only if > authenticated, but how best to serve the actual image file with the > right content-type? > > -jm > > -- > --- John Morrison > --- [email protected] > > -- > You received this message because you are subscribed to the Google Groups > "weblocks" 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/weblocks?hl=en. > > -- You received this message because you are subscribed to the Google Groups "weblocks" 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/weblocks?hl=en.
