Cross-Origin Request Blocked

확인 범위

이 문서는 화면 또는 로그에 표시된 Cross-Origin Request Blocked 문구가 Amazon Web Services 공식 원문의 항목과 일치하는지 확인합니다.

원문 발췌

ormation, see What is CORS?. Determining whether to enable CORS support A cross-origin HTTP request is one that is made to: A different domain (for example, from example.com to amazondomains.com) A different subdomain (for example, from example.com to petstore.example.com) A different port (for example, from example.com to example.com:10777) A different protocol (for example, from https://example.com (새 창에서 열림) to http://example.com (새 창에서 열림)) If you cannot access your API and receive an error message that contains Cross-Origin Request Blocked, you might need to enable CORS. Cross-origin HTTP requests can be divided into two types: simple requests and non-simple requests. Enabling CORS for a simple request An HTTP request is simple if all of the following conditions are true: It is issued against an API resource that allows only GET, HEAD, and POST requests. If it is a POST method request, it must include an Origin header. The request payload content type is text/plain, multipart/form-data, or application/x-www-form-urlencoded. The request does not contain custom headers. Any additional requirements that are listed in the Mozilla CORS documentation for simple requests. For simple cross-origin POST method requests, the response from your resource needs to include the header Access-Control-Allow-Origin: '' or Access-Control-Allow-Origin:'origin'. All other cross-origin HTTP requests are non-simple requests. Enabling CORS for a non-simple request If your API's resources receive non-simple requests, you must enable additional CORS support depending on your integration type. Enabling CORS for non-proxy integrations For these integrations, the CORS protocol requires the browser to send a preflight request to the server and wait for approval (or a request for credentials) from the server before sending the actual request. You must configure your API to send an appropriate response to the preflight request. To create a preflight response: Create an OPTIONS method with a mock integration. Add the following response headers to the 200 method response: Access-Control-Allow-Headers Access-Control-Allow-Methods Access-Control-Allow-Origin Set the integration passthrough behavior to NEVER. In this case, the method request of an unmapped content type will be rejected with an HTTP 415 Unsupported Media Type response. For more information, see Method request behavior for payloads without mapping templates for REST APIs in API Gateway. Enter values for the response headers. To allow all origins, all methods, and common headers, use the following header values: Access-Control-Allow-Headers: 'Content-Type,X-Amz-Date,Authorization,X-Api-Key,X-Amz-Security-Token' Access-Control-Allow-Methods: 'DELETE,GET,HEAD,OPTIONS,PUT,POST,PATCH' Access-Control-Allow-Origin: '' After creating the preflight request, you must return the Access-Control-Allow-Origin: '*' or Access-Control-Allow-Origin:'origin' header for all CORS-enabled methods for at least all 200 responses. Enabling CORS for non-proxy integrations using the AWS

확인 절차

1. 현재 화면 또는 로그에서 Cross-Origin Request Blocked 문구를 확인합니다.
2. 위 원문 발췌와 문구를 비교합니다.
3. 문구가 일치하면 이 문서의 출처 링크에서 적용 환경과 원문 전체를 확인합니다.

주의

이 문서는 문구 식별 범위로 제한합니다. 출처가 직접 설명하지 않는 원인, 설정 변경, 권한 변경 또는 복구 절차를 이 문서만으로 실행하지 마십시오.