2回答
- 新しい順
- 投票が多い順
- コメントが多い順
1
Hi,
this article "CloudFront reverse proxy API Gateway to prevent CORS" https://www.rehanvdm.com/blog/cloudfront-reverse-proxy-api-gateway-to-prevent-cors may help you in fixing your issue.
If you want deeper support from re:Post community, you should provide more details about your issue: error messages, config, etc.
Best,
Didier
0
Postman does not check or enforce cors mechanisms, as that is a browser native feature. Are you handling cors on backend side by allowing origins?
BE will recieve call from gateway only
BE code already have cors policy * attached in common place its just we lept cdn in front of gateway so if same request raised by FE it will reply from its cache rather than calling gateway again
list of api when added with headers that time it is showing cors the header is set('x-api-key', 'xoGxDUvGcI7zzESs15ltz3H4nYzcbHtD17WB2JTz')
'x-api-key', source, source-type, Authorization'
BE will recieve call from gateway only
its just we lept cdn in front of gateway so if same request raised by FE it will reply from its cache rather than calling gateway again