Re: [mapserver-users] How to deal with (visible) CONNECTION information in .MAP file for WMS purposes

2014-01-07 Thread Stefan Schwarzer
Thanks for all the valuable help! If I place the .MAP file somewhere where only the system can read it, the request looks a bit awkward: ….map=/home/include/mapfiles/my_map.map…. Would there a possibility to juste use …map=my_map… and have the path then get added/understood by some internal

Re: [mapserver-users] How to deal with (visible) CONNECTION information in .MAP file for WMS purposes

2014-01-07 Thread Siki Zoltan
Dear Stefan, you can create one wrapper script for each maps file or you can ask only the name (without path) of the map file and your wrapper adds the path to the name. Regards, Zoltan On Tue, 7 Jan 2014, Stefan Schwarzer wrote: Thanks for all the valuable help! If I place the .MAP file

Re: [mapserver-users] How to deal with (visible) CONNECTION information in .MAP file for WMS purposes

2014-01-07 Thread Daniel Morissette
On 14-01-07 5:47 AM, Stefan Schwarzer wrote: Thanks for all the valuable help! If I place the .MAP file somewhere where only the system can read it, the request looks a bit awkward: ….map=/home/include/mapfiles/my_map.map…. Would there a possibility to juste use …map=my_map… and have the path

Re: [mapserver-users] How to deal with (visible) CONNECTION information in .MAP file for WMS purposes

2014-01-07 Thread Steve . Toutant
To use this url http://my_url.org/my_script I would create a file my_script in cgi-bin per example See here http://mapserver.org/fr/cgi/wrapper.html I use a mix of above and this http://mapserver.org/fr/ogc/mapscript.html Steve Stefan Schwarzer stefan.schwar...@unep.org@lists.osgeo.org

Re: [mapserver-users] How to deal with (visible) CONNECTION information in .MAP file for WMS purposes

2014-01-07 Thread thomas bonfort
Would there a possibility to juste use …map=my_map… and have the path then get added/understood by some internal configuration (mod_rewrite perhaps?)? Using that with an environment variable as others have pointed out, or other rewrite techniques from

[mapserver-users] How to deal with (visible) CONNECTION information in .MAP file for WMS purposes

2014-01-06 Thread Stefan Schwarzer
Hi there, I am wondering how to deal with the CONNECTION information in the .MAP which is used for WMS requests. As the .MAP file must be visible and is readable, the CONNECTION information for my database is readable too. # Layers definition - LAYER

Re: [mapserver-users] How to deal with (visible) CONNECTION information in .MAP file for WMS purposes

2014-01-06 Thread Siki Zoltan
Hi Stefan, you should hide your map file using a wrapper script on the server side. See http://mapserver.org/cgi/wrapper.html You can find some other methods at http://mapserver.org/ogc/wms_server.html look for Changing the Online Resource URL Regards, Zoltan On Mon, 6 Jan 2014, Stefan

Re: [mapserver-users] How to deal with (visible) CONNECTION information in .MAP file for WMS purposes

2014-01-06 Thread Håvard Tveite
Your MAP file does not have to be visible to / readable by the web server, but it must be visible to Mapserver (mapserv). Håvard On 1/6/2014 10:16 AM, Stefan Schwarzer wrote: Hi there, I am wondering how to deal with the CONNECTION information in the .MAP which is used for WMS requests. As

Re: [mapserver-users] How to deal with (visible) CONNECTION information in .MAP file for WMS purposes

2014-01-06 Thread Lime, Steve D (MNIT)
You can also encrypt the database password using MapServer utilities. I do the following: - store the mapfiles outside web htdocs directory - encrypt database passwords (if in a shared hosting environment) - use webserver environment variables to reference mapfiles... this obfuscates your

Re: [mapserver-users] How to deal with (visible) CONNECTION information in .MAP file for WMS purposes

2014-01-06 Thread Jeff McKenna
On 2014-01-06 10:39 AM, Lime, Steve D (MNIT) wrote: You can also encrypt the database password using MapServer utilities. I do the following: - store the mapfiles outside web htdocs directory - encrypt database passwords (if in a shared hosting environment) - use webserver