Why isn't the default for cflocation addtoken equal to no?

Question

Is there any good reason why the default for this tag would be yes? It seems to be that it should almost always be no. I am missing something?

Answer 1

If I recall correctly, the only reason for it being that way is for some backward compatibility issues way back in something like version 1.0 where originally, you had to always pass that information around to maintain your application state.

When the technology moved on, they added the addtoken attribute but left the default so it wouldn't break a bunch of existing code. Now, it's sort of like our appendix and is not used for much. They could probably change the default at this point without much impact.