Mellon envs pointed to the same saml attribute

[MrAtheist]

Hello, i would like to double check the behavior of the following...

MellonSetEnvNoPrefix "ENV1" "urn:oid:0.9.2342.19200300.100.1.1"
MellonSetEnvNoPrefix "ENV2" "urn:oid:0.9.2342.19200300.100.1.1"

In this case it does appear that ENV1 == null and ENV2 contains the actual value?

# very un-scientific approach...

LogFormat "%a %l %{ENV1}e %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\""

# %{ENV1}e is printed as a literal dash `-`
# ${ENV2}e does print out the value

Is this the expected behavior?

[thijskh]

I think this is expected. The config parameter is in documentation described as a 'mapping' or 'rename' of the attribute. So basically it indeed changes the name it's known by, it does not copy it into the new name. I understand this was not clear to you, maybe you could suggest additional wording for the documentation?

[a-n-d-i]

Yeah, it's a different behavior to what bash does, for example. So it'll get folks... How about "Unlike env variables in the bash shell, MellonSetEnvNoPrefix renames Variables. So, for example, MellonSetEnvNoPrefix "ENV1" FOO renames FOO to ENV1 and all references to FOO will be null forthwith.

[MrAtheist]

noted, sort of like a last "env" standing wins