Story: Use Akamai for 404 Responses.

[bryanpizzillo]

As a [role], I want [feature], so that [benefit]

We will no longer update content on the old site, our 404 has page content. So we need the service to return a 404 code, but not care about any markup. Akamai will see the 404 and serve up the appropriate page of content. INSERT DIGITAL PLATFORM STORY HERE

First, do we actually have 404s on the legacy content. If we do configure, Akamai to get the 404 from Drupal or something.

This is to support whatever weirdness around: <add name="PageNotFoundHandler" verb="GET" path="PageNotFound.aspx" type="NCI.Web.CDE.HttpHandlers.PageNotFoundHandler,NCILibrary.Web.ContentDeliveryEngine" />

ESTIMATE 4-5 days. Some investigation has been done as part of a digital platform 404 fix.

Acceptance Criteria

Scenario: [title]
  Given [context]
    And [some more context]
  When  [event]
  Then  [outcome]
    And [another outcome]

Resources:

• Feature: JIRA Ticket #
• Mockups: Here goes a URL to or the name of the mockup(s) in inVision
• Web Page: Here goes a URL to an existing web page

Notes

Some complementary notes if necessary:

• Here goes a quote from an email

• Here goes whatever useful information can exist…

---

Solution

Prerequisites

• required dependency for identifying the problem, scope and then solution for this issue
• [ ] Short Spike Description - Issue #9999

Tasks

• [ ] Short Task Description - Issue #9999
• [ ] Short Task Description - Issue #9999

Technical Notes

• More notes, or technical nuances/direction

[blairlearn]

Possible approach:

Instead of potentially hitting the Acquia servers on every 404 error, we set up a static 404 page in NetStorage (with nightly updates) and serve that page anytime the legacy services report a 404 error. (Potentially, this could be expanded to put themed 404 pages on any static file type which presently results in an "ugly" error. e.g. https://www.cancer.gov/chicken.jpg)

Create a new "Static Asset" NetStorage location.

• Create an "error-pages" sub-directory.
• What tiers are needed? Just production and dev/staging? Or just production?

Create a new Akamai rule based on the "Forward to Alternate Host" template.

This rule would be a descendant of the one which routes traffic to the "legacy services" origin.

• Condition: "Response Status Code" is one of 404 (others?)
• Behavior: Site Failover with action set to "Serve alternate content from NetStorage." Serve a 404 page from the "Static Assets" group (see below).

Generate and maintain a themed 404 Page

• Designate a location in Drupal as "this is where the 404 page will be and we will never put content at this location." (e.g. www.cancer.gov/real-error-page-with-a-random-string)
• Create a cron job on the service operations VM to run curl -X GET https://www.cancer.gov/real-error-page-with-a-random-string and upload the output to NetStorage.