Default pages bug in 3.2.3?

[Cantor, Scott]

Actually, I'm puzzled, because based on the code, this shouldn't be happening. The duplication of the values is only something that appears to affect the attribute export step. The "built-in" variables are just applied with a call that ends up calling SetServerVariable or SetHeader directly, not appending to pre-existing state.

So there should not have been any duplication introduced by the security fix and I have no idea what you're seeing here.

If by some chance you're actually using the workaround I mentioned with the Assertion attribute extractor instead, then that would result in duplication, but setting the option to block export of duplicate attribute values would address that.

If that option didn't work for the attributes, then that would explain the other duplication as well but it did for me and for others that applied that as a workaround for Microsoft's bug.

-- Scott