From 4426e9dfd4b2e3172c840e1e75ecc800fe1b3b66 Mon Sep 17 00:00:00 2001 From: g-pan Date: Mon, 25 Sep 2023 17:37:54 -0400 Subject: [PATCH] HPCC-28033 Document CORS Section of values.yaml Signed-off-by: g-pan --- .../ContainerizedMods/ConfigureValues.xml | 35 +++++++++++++++++++ 1 file changed, 35 insertions(+) diff --git a/docs/EN_US/ContainerizedHPCC/ContainerizedMods/ConfigureValues.xml b/docs/EN_US/ContainerizedHPCC/ContainerizedMods/ConfigureValues.xml index a8d5d801290..e7349941fa8 100644 --- a/docs/EN_US/ContainerizedHPCC/ContainerizedMods/ConfigureValues.xml +++ b/docs/EN_US/ContainerizedHPCC/ContainerizedMods/ConfigureValues.xml @@ -1023,6 +1023,41 @@ thor: categories, including the "ecl" category, are read internally by system components and not exposed directly to ECL code. + + + Cross Origin Resource Handling + + Cross-origin resource sharing (CORS) is a mechanism for + integrating applications in different domains. CORS defines how client + web applications in one domain can interact with resources in another + domain. You can configure CORS support settings in the ESP section of + the values.yaml file as illustrated below: + + esp: +- name: eclwatch + application: eclwatch + auth: ldap + replicas: 1 + # The following 'corsAllowed' section is used to configure CORS support + # origin - the origin to support CORS requests from + # headers - the headers to allow for the given origin via CORS + # methods - the HTTP methods to allow for the given origin via CORS + # + corsAllowed: + # origin starting with https will only allow https CORS + - origin: https://*.example2.com + headers: + - "X-Custom-Header" + methods: + - "GET" + # origin starting with http will allow http or https CORS + - origin: http://www.example.com + headers: + - "*" + methods: + - "GET" + - "POST" +