Headers and Helix Configs in EDS Site created with Edge Delivery Services Template (universal editor , xwalk project)

[josepha18283197]

I have created an EDS site using the "AEM Site with Edge Delivery Services Template 0.0.16" and set up configurations and headers within it. The paths JSON file in the repository has the necessary mappings. I can access the Helix config via main--**.aem.page/config. json, but any updates made and republished do not show up in the config JSON. Additionally, when attempting to load headers JSON via main--**.aem.page/headers. json, I receive a 404 error.

@arunpatidar 

[arunpatidar]

Hi @josepha18283197 

header config file is use to apply custom HTTP response headers to resources, for example to allow CORS.

You can see those headers in the page request.

Please check below for more details

https://www.aem.live/docs/custom-headers 

[josepha18283197]

Hi @arunpatidar 

 Yes. But as per the documentation https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/edge-delivery/wy... , metadata, config, redirects all can be accessible like ....aem.page/metadata.json, ...aem.page/redirects.json. Because we are doing the path mapping in paths.json.  Likewise, is headers not accessible using this url (....aem.page/headers.json)? 

[arunpatidar]

Hi @josepha18283197 
I don't think so you should allowed below paths accessible over browser, those are config for the System.

Example if you are going to expose config json, you would endup exposing sensitive data:

https://www.aem.live/docs/configuration 

• Configuration: /.helix/config.json
• Headers: /.helix/headers.json