Last Updated: October 22, 2024
This document helps you understand the process of a VA.gov to Subdomain redirect. This is a page-level cross-domain redirect. For more information about redirects, return to the Redirect Implementation Strategy page.
The Sitewide Content, Accessibility & Information Architecture team (CAIA) reviews all URL redirects before routing them to the appropriate engineer.
Before you attempt a redirect, follow these two important steps:
-
Read the Design System guidance for redirects.
This is a server-side redirect
VA.gov to Subdomain redirects are server-side redirects. A server-side redirect sends a status code to the browser. This status code lets the browser know that the requested page has moved – or is no longer available – and points the browser toward the page’s new URL. Server-side redirects can be temporary or permanent.
Server-side redirects are preferred.
Information Table: VA.govto Subdomain Redirects
Below is a table that outlines the details of a VA.gov to Subdomain redirect.
|
|
|
|
When to use this redirect: |
When a single page within |
|
Real world example: |
redirects to
|
|
How it works: |
Traffic to |
|
Code example: |
|
|
Additional Info: |
Refer to the revproxy README for more information on conventions and considerations, such as trailing slashes, child pages, and case sensitivity. |
|
Team Responsibilities: |
CAIA must sign off on request. |
Additional Resources
-
To learn more about redirects, visit Redirect Implementation Strategy page.
-
To learn about redirects involving Drupal, visit Drupal Redirects.
-
For information on redirecting forms like PDFs, visit Redirecting static documents.
-
For any questions regarding redirects, contact the CAIA team in their Slack channel #sitewide-content-accessibility-ia.
Help and feedback
-
Get help from the Platform Support Team in Slack.
-
Submit a feature idea to the Platform.