> From: Carl Dreher [mailto:focus...@arn.net] > Subject: restricting access to images
> I need to restrict access to a website's images, to people that have > logged on, have authorization etc. I've searched though the Tomcat > user's mailing list archives and didn't find a discussion that addressed > this, so I thought I'd asked for some architectural guidance. A prerequisite for doing anything with Tomcat is to read the servlet spec for the version you're using (which you didn't tell us). You will find a section in there on security, documenting the means to control access to resources. > If I write a servlet such as the above, is there ever only once instance > of it running? Don't confuse objects with threads. There is one instance of a particular servlet, but many threads may be executing in it concurrently, with each thread processing a separate request. > I'd like to offer a suggestion: In multiple places, the FAQs about using > this list have comments such as "...be sure to check the archives before > asking a question..." but don't have any links (or instructions) on HOW > to do that! There's no point in repeating something in a myriad of places that you must have already read in order to sign up for the mailing list. As clearly stated on the mailing lists page (http://tomcat.apache.org/lists.html): "Formatted archives are available in several places including the Apache Mail Archives, MARC, Nabble, and MarkMail. The raw mbox files are also available." - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
