Opened 15 years ago
#3122 new enhancement
use of environment variables in connection/data string
Reported by: | mko | Owned by: | sdlime |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | MapServer C Library | Version: | 5.4 |
Severity: | normal | Keywords: | environment variables, getenv |
Cc: | mko |
Description
Currently, one use variable substitutions to make a mapfile behaving dynamically. If you do not want a user to adapt mapfile parameters but your program logic (e.g. a prepended wrapper), substitutions shouldn’t be used as a user could override it.
Environment variables could be used to e.g. use the username of an authenticated user in the data statement or to hold passwords for databases if you want to share a mapfile across different hosts with different passwords.
Attachments (1)
Note:
See TracTickets
for help on using tickets.
Same placeholders as crypted strings, e.g. {REMOTE_USER} in order to avoid multiple search runs; may be confusing for users if they have a variable name in hex sytle like {EFEF} which would be treated as a crypted string.