Using the X-Schema-Version sometimes returns a wrong schema version.
This is probably caused by a wrong CloudFront configuration. CloudFront (which is used as a cache in front of the API) does not use the X-Schema-Version as part of the cache key per default, so it will return wrong schema versions if it has any request cached.
X-Schema-Version is also missing from the Vary header (which CloudFront ignores, but other layers in between (for example browser cache) might care about).
Expected Behavior
CloudFront should be configured to use the X-Schema-Version as part of the cache key
X-Schema-Version should be added to Vary
Steps To Reproduce
No response
Happening since
Always
Anything else?
For API consumers: Always use the v query parameter instead of the X-Schema-Version header to make sure the correct schema is used.
Current Behavior
Using the
X-Schema-Versionsometimes returns a wrong schema version.This is probably caused by a wrong CloudFront configuration. CloudFront (which is used as a cache in front of the API) does not use the
X-Schema-Versionas part of the cache key per default, so it will return wrong schema versions if it has any request cached.X-Schema-Versionis also missing from theVaryheader (which CloudFront ignores, but other layers in between (for example browser cache) might care about).Expected Behavior
X-Schema-Versionas part of the cache keyX-Schema-Versionshould be added toVarySteps To Reproduce
No response
Happening since
Always
Anything else?
For API consumers: Always use the
vquery parameter instead of theX-Schema-Versionheader to make sure the correct schema is used.