From fdda33713520f9982b5f214bdf941cac8b64affb Mon Sep 17 00:00:00 2001 From: "Michael[tm] Smith" Date: Tue, 9 Mar 2021 15:17:44 +0900 Subject: [PATCH] Fix missing words in Access-Control-Expose-Headers (#2963) --- .../web/http/headers/access-control-expose-headers/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/en-us/web/http/headers/access-control-expose-headers/index.html b/files/en-us/web/http/headers/access-control-expose-headers/index.html index c7deea708890c41..bca7f8ac5ff2133 100644 --- a/files/en-us/web/http/headers/access-control-expose-headers/index.html +++ b/files/en-us/web/http/headers/access-control-expose-headers/index.html @@ -9,7 +9,7 @@ ---
{{HTTPSidebar}}
-

The Access-Control-Expose-Headers allows a server to indicate which response headers should be made available to scripts running in the browser, in response to a cross-origin request.

+

The Access-Control-Expose-Headers response header allows a server to indicate which response headers should be made available to scripts running in the browser, in response to a cross-origin request.

Only the {{Glossary("CORS-safelisted response header", "CORS-safelisted response headers")}} are exposed by default. For clients to be able to access other headers, the server must list them using the Access-Control-Expose-Headers header.