Consider whether to switch to non-caching HttpClient in dynamic provider
Basics
Logistics
Basics
Logistics
Description
We might want to consider switching the default client in the DynamicHTTP provider to the non-caching variant if we think it’s causing confusion or unusual results due to inadvertent use of caching headers that people might not be aware are even there.
Environment
None
Activity
Brent Putman
October 18, 2024 at 9:06 PM
Discussed on call. Will probably just add a flag to determine which one is used.
We might want to consider switching the default client in the DynamicHTTP provider to the non-caching variant if we think it’s causing confusion or unusual results due to inadvertent use of caching headers that people might not be aware are even there.