SPIKE: Determine what the process is for a 301 redirect

[loripusey]

Tasks

• Locate 301 redirect intake from CAIA
• Determine timing and process
• Document process/findings/resources

[cgednalske]

Overview

Important notes:

Timing:

Implement redirects at the time the URL changes. Plan to implement the redirect to coincide when the URL of the original page changes so visitors do not encounter a page not found (404) error. The redirect should be implemented no later than 24 hours from when the new URL goes live.

Steps:

• Redirect will be assigned to our team after the request is approved

Before you attempt a redirect, follow these two important steps:

• File a redirect request ticket on GitHub.
• Read the Design System guidance for redirects.

CAIA approves requests and assigns it to the appropriate team. Requesting team may be responsible for the redirect code change, and is responsible for communication with VA stakeholders as needed.

Type:

We are doing the following Server-side redirect:

• Redirect: VA.gov to VA.gov page-level redirect
• Explanation: A page on our servers redirects to another page on our servers
• Server/Client: Server-side
• Difficulty: Low

Redirect Materials

• Redirect ticket
• VA Design Standards > URL Redirects
• Developer documentation > Redirect Implementation Strategies
• Redirects README with code examples for server-side redirect

For further questions

CAIA Slack thread

Timeline

Implement redirects at the time the URL changes. Plan to implement the redirect to coincide when the URL of the original page changes so visitors do not encounter a page not found (404) error. The redirect should be implemented no later than 24 hours from when the new URL goes live.

From request ticket:

Requests must be submitted AT LEAST 2 weeks in advance. Some requests take a significant amount of time and coordination to implement, so start the process as soon as you know you will need one.

• This issue will be used from initial request through implementation to ensure all individuals working on this are notified of status updates. Please do not create multiple issues to track different steps.
• It is your responsibility to notify VA stakeholders as appropriate.

We can choose from the following when submitting the request:

Implementation date

When does this request need to be live? NOTE: Redirects in vsp-platform-revproxy auto-deploy M-Th. Friday launches should be avoided.
Choose one:

• On a specific date, connected to a program or publishing requirement. DATE:
• Any day prior to a deadline/latest possible date. DEADLINE:
• Any day after an earliest possible date. EARLIEST DATE:
• During a specific date range: EARLIEST DATE TO LATEST DATE:
• No hard timing requirements, publish when possible.

[cgednalske]

@loripusey I've documented everything needed for us to go through the process for the 301 redirect. I think we can close this out and are good to move forward with completing the request (Create 301 redirect ticket) at any point 👍