Mega Menu Issue for dceg2

[laurelthrash]

Make an Akamai configuration rule to solve the issue reported in CGOV-17623. This issue was reported via Jira, and discussed via Slack. Via Slack it was determined that we should make an Akamai configuration rule to address the issue. [Link to Slack conversation here].

Full reported issue in Jira is:

IMS has updated DCEG2 to match our redesign, but they are getting an error with the megamenu. They think the error can be resolved if we change the Access-Control-Allow-Origin settings to allow https://dceg2.cancer.gov.

For details, here's what they wrote to me:

We have incorporated the DCEG redesign into the DCEG2 pages. However, we are noticing an issue on DCEG2 pages when attempting to open the top navigation megamenu or mobile navigation menu. Example:

“Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://dceg.cancer.gov/taxonomy/term/301962/mega-menu. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 200”

For now we are bypassing the megamenu in favor of direct links to section homepages. We believe the issue can be resolved if you change the Access-Control-Allow-Origin settings to allow https://dceg2.cancer.gov/

Parent Issue: CGOV-17623

Sub-Tasks [To be adjusted as needed]

• [ ] Write Akamai rule
• [ ] Test rule to ensure mega menu issue is resolved
• [ ] Implement Rule
• [ ] Notify Alex via Jira ticket [PM/Laurel]

Notes

*[Insert notes here, once available]

[andyvanavery]

@bennettcc please investigate this issue further