TNT-49972 - Fix ODD rules request proxy caching issue

[dcottingham]

Description

Added new ODD configuration option (shouldArtifactRequestBypassProxyCache). When enabled and a proxy is configured, send empty Authorization header on artifact rules request to bypass proxy-level cache.
Even though this request does not require an Authorization header, it's a workaround to bypass the proxy cache since proxies know not to cache responses for authorized requests.

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have signed the Adobe Open Source CLA.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[jasonwaters]

@dcottingham when shouldArtifactRequestBypassProxyCache is set to true, does it mean that every artifact request will have the Authorization header and therefore there will never be caching? If so, maybe it makes more sense to rename the property to something like disableOddArtifactCache? 🤷‍♂️

I still think this customer should just fix their caching issues internally. but it's not a hill i'll die on.

[dcottingham]

@dcottingham when shouldArtifactRequestBypassProxyCache is set to true, does it mean that every artifact request will have the Authorization header and therefore there will never be caching? If so, maybe it makes more sense to rename the property to something like disableOddArtifactCache? 🤷‍♂️

I still think this customer should just fix their caching issues internally. but it's not a hill i'll die on.

Yes, every request will include the Authorization header and there won't be any caching inside the customer's proxy, but Akamai will still do caching based on the Etag mechanism. That's why I was more explicit with the naming. But if you think it's more clear to name it disableOddArtifactCache I can do that.

[jasonwaters]

fine by me if you want to merge this