make known users anonymous / wp_cache_make_known_anon does not respect wp_rejected_uri strings or Accepted Filenames & Rejected URIs

make known users anonymous / wp_cache_make_known_anon does not respect wp_rejected_uri strings or Accepted Filenames & Rejected URIs.

This may be the opposite of what users expect: when certain pages are excluded from caching, there is no point in stripping the login information from these requests in order to serve a cached page.

In fact, stripping this information from pages which should be cached might break their functionality, which means the 'make known users anonymous' setting cannot be used safely.

see also:
- Automattic/wp-super-cache#422 DOING_AJAX not checked
- Automattic/wp-super-cache#937 make known users anonymous breaks Rest API

Start with wp_cache_make_known_anon and trace how the wp_rejected_uri strings and Accepted Filenames & Rejected URIs settings are applied. Compare that behavior with the related DOING_AJAX and REST API issues linked in the report. Done should mean excluded requests retain the login information needed for their functionality instead of being made anonymous.

Written by the indexing model from the issue text.