Add an option to disable the static cache of the endpoint base

[rogertheriault]

for users who need fine-grain control over the endpoint base, this allows selective or site-wide disabling of the static cache.

The static variable results in subsequent requests for the endpoint base bypassing any url filters.

This might be needed for a site that uses more than one domain, for example a different domain for wp-admin vs the front end.

This was deployed to SVN in r350550 on 2018-08-15

[mjangda]

Should the static cache just be removed? How expensive is it to build the endpoint base?

[rogertheriault]

I was thinking it should probably be dropped, but was not keen to break someone's site if they'd set up some elaborate filtering to get around the inability to filter :-) so @rebeccahum suggested just adding a filter that could be used just by affected sites.

I'm not clear why it was there. Static caches are handy but maybe not so handy for something that folks expect to be able to filter. It doesn't look like it saves that much processing.

But removing it entirely is probably something for a future release by @philipjohn

[philipjohn]

for users who need fine-grain control over the endpoint base, this allows selective or site-wide disabling of the static cache.

Do we know of any one wanting to do this, or is it just a thing we think people might want?

[rogertheriault]

Do we know of any one wanting to do this, or is it just a thing we think people might want?
Only the folks we implemented the filter for in SVN right now. I'm ok with just removing the static cache instead, if it's unnecessary.