Not too long ago, during the post-update smoke tests of a client’s upgrade to Sitecore 8.1 Update 2, we came across an issue where URL requests were “magically” being resolved to content items that clearly should not have. After an exhaustive search online for some sort of direction — or even encountering someone facing this identical issue — I decided it was time to grep the configuration files and came across this:
After setting ItemResolving.FindBestMatch to Disabled the URL requests were back to resolving to their proper content items as expected from previous versions.
Not being completely satisfied with simply disabling this new setting Sitecore felt important enough to include in Sitecore 8.1 Update 2, I felt it was time for a revisit…and wouldn’t you know:
Hopefully this is resolved in Update 4.