Full site redirect from Subdomain to VA.gov
Last Updated: October 22, 2024
This document helps you to better understand a full site redirect from a Subdomain to VA.gov. 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
Full site, Subdomain to VA.gov 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.
Full site, Subdomain to VA.gov redirects are complex redirects with a HIGH degree of difficulty.
Information Table: Full site redirects from Subdomainto VA.gov
Below is a table that outlines the details of a full site, Subdomainto VA.gov redirect.
Full site redirects from | |
When to use this redirect: | When a full site is ready to migrate content to the modernized
|
Real world examples: |
|
How it works: | Option 1: The platform team takes control of the entire subdomain. Traffic to Option 2: For a .NET website, modify the .NET web.config (XML file). Example: Option 3: If a full site is in TeamSite, the WebOps team can redirect the site. Follow WebOps KB article steps (PIV required to access) to request the redirect. |
Additional Info: | This redirect is dependent on VA stakeholders. Authority to Operate (ATO) and Enterprise Security External Change Council (ESECC) approval must be considered. |
Team Responsibilities: | If a subdomain or .NET site: The owners of the public website are responsible along with Platform Devops, and whatever veteran-facing team requests the redirect. If a TeamSite: WebOps is responsible along with whatever veteran-facing team requests the redirect. |
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.