Vets.gov cross-domain redirect: Page-level redirect from Vets.gov to VA.gov
Last Updated: October 22, 2024
This document helps you to better understand page-level redirect from Vets.gov
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
Page-level redirects from Vets.gov
to VA.gov
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: Vets.gov
cross-domain redirect
Below is a table that outlines the details of a page-level redirect from Vets.gov
to VA.gov
.
| |
When to use this redirect: | When |
Code location: | Code is in the devops repo: vetsgov-redirects.yml
|
Additional Info: | We should no longer see redirects like this.
|
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.