the recently added Accept-Language Header seems to be bugged.
I am randomly receiving differently localized responses for the H5 Metadata API. I was able to reproduce this in the Web Interface with the H5 Campaign Missions api.
Most of the time its english, but sometimes i get German or French.
The argument “en” does not seem to be respected. Is it possible the Locale should be “en-US”?
Hi HyperSunbro! Thanks for reporting this bug. We had our caching policies configured incorrectly for the Metadata Operations that accept the Accept-Language HTTP header. We would ignore the Accept-Language header when caching.
I believe that the behavior you were seeing was that somebody would have requested Campaign Missions with the Accept-Language header of “de”. When you issued your request without specifying the header or with specifying “en”, we would return the cached response, which had German content.
I’ve updated the caching policy for all of the Metadata Operations and confirmed that it’s working correctly for Campaign Missions.
Thank you for catching this issue. If you have any further issues, please let us know.