Open djgarr opened 4 months ago
Since the original link was a named anchor link www.fec.gov/regulations/#something, the redirect won't see anything after the #. We may be able to handle it on the application side though, meaning the CMS application would read the request and handle it using some application logic. But that's going to take some thought.
The redirects currently in place for the eCFR (11 CFR 300.32(a)(3) and (4)), for example, takes you to the main citation, not the sub-citation. The way the link anchors appear to work on the eCFR website appears to be different than the ones in the redirect (https://www.ecfr.gov/current/title-11/part-300/section-300.32#p-300.32(a)(3))
Tech considerations:
Proxy redirects currently do not recognize anything after the '#' symbol, can we handle this with app logic, or some other creative way? See comment below.
Completion criteria: