Hello,
I am trying to set the channel for our upgrade environment which was cloned from the production one, and so far, i was able to add the mount configurations into the cms/console but the channel is throwing CORS issue, trying to access the production endpoint ( see this error )
Access to XMLHttpRequest at ‘https://site.becn.com/resourceapi/site/_cmsinternal’ from origin ‘https://cms-test.becn.digital’ has been blocked by CORS policy: The ‘Access-Control-Allow-Origin’ header has a value 'https://www.becn.com’ that is not equal to the supplied origin.
My console configurations are the next ones :
/hst:hosts:
jcr:primaryType: hst:virtualhosts
jcr:uuid: d75ab8b4-69ad-457e-8160-c9311ab2b20f
hst:defaultcontextpath: /site
/proplus-upgrade:
jcr:primaryType: hst:virtualhostgroup
jcr:uuid: a9646850-1302-496e-bfed-18262d313ec3
hst:cmslocation: https://cms-test.becn.digital
/digital:
jcr:primaryType: hst:virtualhost
jcr:uuid: d9580bc8-7778-41f8-913c-f9d55b80106a
/becn:
jcr:primaryType: hst:virtualhost
jcr:uuid: 2e26c530-3316-4d34-b570-69579f7136c4
/cms-test:
jcr:primaryType: hst:virtualhost
jcr:uuid: 3fb77bfe-f577-4c19-8041-5e1edd1112e2
/hst:root:
jcr:primaryType: hst:mount
jcr:uuid: aba6ab79-261f-4954-95ea-1f1641f48d82
hst:homepage: root
hst:mountpoint: /hst:hst/hst:sites/beaconhippo
hst:pagemodelapi: resourceapi
hst:responseheaders: [‘Access-Control-Allow-Origin: https://cms-test.becn.digital’,
‘Access-Control-Allow-Credentials: true’, ‘Access-Control-Allow-Headers:
content-type’, ‘Access-Control-Expose-Headers: Is-Product-Page, Product-ID,
Item-Number’]
hst:scheme: https
hst:showcontextpath: false
/proplus-upgrade-proxy:
jcr:primaryType: hst:virtualhostgroup
jcr:uuid: 5120a6ff-8d6c-417b-a3cf-c4cecca5f9ff
hst:cmslocation: https://cms-test.becn.digital
/digital:
jcr:primaryType: hst:virtualhost
jcr:uuid: 11c86524-e313-4a4c-86e5-a2bd982b3f8c
/becn:
jcr:primaryType: hst:virtualhost
jcr:uuid: 7ea1d039-75b3-4306-b1f4-afca97876142
/site-test:
jcr:primaryType: hst:virtualhost
jcr:uuid: dd9fafd8-416e-4411-b914-776f34c24776
/hst:root:
jcr:primaryType: hst:mount
jcr:uuid: 7de8723b-6564-4bab-8fa6-fa1e109b28b4
hst:homepage: root
hst:mountpoint: /hst:hst/hst:sites/beaconhippo
hst:pagemodelapi: resourceapi
hst:responseheaders: [‘Access-Control-Allow-Origin: https://cms-test.becn.digital’,
‘Access-Control-Allow-Credentials: true’, ‘Access-Control-Allow-Headers:
content-type’, ‘Access-Control-Expose-Headers: Is-Product-Page, Product-ID,
Item-Number’]
hst:scheme: https
hst:showcontextpath: false
/api:
jcr:primaryType: hst:mount
jcr:uuid: 7be3c571-3ca6-4244-8b3f-29e8798904d6
hst:alias: api
hst:ismapped: false
hst:namedpipeline: RestApiPipeline
hst:types: [rest]
/api-man:
jcr:primaryType: hst:mount
jcr:uuid: 8e2e34f7-83c2-4fc6-aac2-17df4a39ce42
hst:alias: api-man
hst:ismapped: false
hst:namedpipeline: JaxrsRestPlainPipeline
hst:types: [rest]
Do you know what might be the issue that is causing the channel to access the production endpoint instead of the upgrade environment endpoint ?
Thank you