I don’t know if this is the proper forum, if not, excuse me.
I have in one NT machine Apache Web Server and Tamino 1.2.1.5 DB.
When the application access to Tamino DB it does through the following URL: http://localhost/tamino/database_name/_XQL … I can control access to the tamino virtual directory in Apache so nobody from Internet can access directly to my DB.
Tamino 1.2.1.5 is very old now, the current version of Tamino is 2.3.1.x. This version of Tamino has a security feature which should solve your problem.
Yes, I know it’s an old version, but by the moment is the one I have. I’m trying to acquire the last version but, by the moment, I don’t have the money.
You were right, even when a virtual path is not defined specifically in Apache, I’m able to set special rights to it.
I have set deny access (except localhost) to the parent directory of the images’ path (/tamino) and allow rights to everybody for the virtual path where images are stored in the DB (/tamino/database/images)
The problem refered in the tamino 1.2.1.5 does not look to be solved in version 2.3.1.4. It looks as if the only way to restrict access to nonXml documents is by playing with the apache configuration. Quite painful. I really hope to be wrong but it looks as if tamino security does not get involved whenever you try to access any information with a plain URL’s. Trying to explain myself. Having a xml object:
