Gmail team has found out that this endpoint is returning inconsistent Access-Control-Allow-Origin header. It could be because it enables public cache. The problem is that this header depends on the origin header and therefore it cannot properly be cached without messing the response header up. This PR disables the cache on the Netlify. Given it is only a demo, I do not expect this to become a significant cost problem.
Gmail team has found out that this endpoint is returning inconsistent Access-Control-Allow-Origin header. It could be because it enables
publiccache. The problem is that this header depends on the origin header and therefore it cannot properly be cached without messing the response header up. This PR disables the cache on the Netlify. Given it is only a demo, I do not expect this to become a significant cost problem.@zhangsu