They are being cached, but this does not stop the fact that I still require a first request to determine the URL a user’s avatar, a request that is not cached. Attempting to cache it makes the request not process correctly (Send OPTIONS, but not GET)
After making this request though, If I use the users’ avatar image, if it’s being used before, it is properly cached as the browser would behave normally.
Having an API point for this will not only bypass this first request, but is, in many implementations, handled by cache. Since a browser can handle a 303 redirect to fetch from cache