MapAddress directive added to torrc doesn't work for some websites, fails to assign specified exit node
Please refer to this thread on the TOR Stack Exchange: https://tor.stackexchange.com/questions/19647/how-are-certain-websites-able-to-override-the-specific-exitnode-you-chose-and-c
If I add the following to my torrc (and restart TOR):
MapAddress ayefiles.com ayefiles.com.719FD0FA327F3CCBCDA0D4EA74C15EA110338942.exit MapAddress duckduckgo.com duckduckgo.com.719FD0FA327F3CCBCDA0D4EA74C15EA110338942.exit
then I see that if I visit https://duckduckgo.com/, I'm correctly assigned to use exit node 18.104.22.168, which corresponds to the fingerptint. However, if I visit https://ayefiles.com, my exit node will NOT be 22.214.171.124, but instead can be any exit node such as 126.96.36.199 or 188.8.131.52, and will even change if I do a Ctrl+L to get a "New Tor circuit for this site" which should be a no-op for sites with MapAddress directives mapping them to a single exit node.
How is ayefiles.com able to hack TOR and prevent it from applying the requested exit node? Can we stop this from happening?
Finally, if for some reason this is "expected behavior" (though I can't fathom how) please change this to a feature request to add a way to specify a single exit node in a similar way to MapAddress, except that can't be hacked.