Developer docs
Developer docs
Breadcrumbs

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:

  1. File a redirect request ticket on GitHub.

  2. 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.

Vets.gov cross-domain redirect: Page-level redirect fromVets.gov to VA.gov

When to use this redirect:

When from URL domain is vets.gov

Code location:

Code is in the devops repo: vetsgov-redirects.yml

  • Any Platform or VFS engineer with repo access may modify.

  • There are options for rewrite and retain_path. If you have questions on what values to use for those options, you can reach out to VSP Devops and the redirect request's stakeholder(s) for clarity.

Additional Info:

We should no longer see redirects like this.

  • Vets.gov redirects were common during the era when we were actively migrating Vets.gov content to VA.gov content. That era is over.

Team Responsibilities:

CAIA must sign off on request.

Additional Resources

Help and feedback