I'm seeing issues with caching response headers. Initially, while developing locally a response will have the `Access-Control-Allow-Origin` set to `http://localhost:3000`. If I switch over to my staging environment, the response is cached with that header, which obviously does not match the origin, and the request is blocked. This also happens in the reverse (cached headers on staging prevents local requests). I could see this perhaps happening across subdomains as well?
It seems there should be a `Vary: Origin` response header present. Is there something I can do on my end to handle this?
Please sign in to leave a comment.