-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Redirect Request: VHA /healthbenefits redirects - 11/30 target #11680
Comments
@mnorthuis Feel free to add any additional notes here! |
Does this still need review from Joni / Randi, or it's ready for PW to implement? |
These are ready to go, @jilladams . |
@chri5tia reopening. We have 3 redirects with unexpected behavior: the redirects were implemented in code in a way that seems logical, but actual end landing page has broken redirects
possible culprit?spitballing, but does https://github.com/department-of-veterans-affairs/devops/blob/master/ansible/deployment/config/revproxy-vagov/vars/redirects.yml#L17 maybe somehow have an impact here? |
https://www.va.gov/healthbenefits/access/health-care/about-va-health-benefits/ The redirect that @jilladams pointed out could be related but its backwards. (/healthbenefits/access/ is being interjected in front of instead of instead of).
Did I put something in the code here to concatenate instead of replace? |
The issue is of 'relative' redirects. Each of the non-functional redirects share the same trait: they are missing a forward slash preceding the dest:
Without the preceding "/" results in a "relative redirect" by nginx. With the preceding slash:
|
Instructions
Type of request
Implementation date
When does this request need to be live: November 30, 2022 or before
Redirects
2 notes on these redirects:
Vanity URLs
Link to campaign landing page request issue:
Process, Roles and Responsibilities
The text was updated successfully, but these errors were encountered: