revert: /privacy-policy back to /privacy - #473
Merged
Merged
Conversation
Checked live, read-only, on both dev.civicdataspace.in and civicdataspace.in: /privacy returns 200 on both; /privacy-policy 307-redirects to login on both. /privacy was the real, already-working route before #472 -- that PR's diagnosis was backwards. This undoes the proxy.ts allowlist entry and the footer link change from #472, keeping the skip_provider workflow change (unrelated, still correct).
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#472's diagnosis was backwards. Checked live, read-only, on both environments just now:
dev.civicdataspace.in/privacy-> 200dev.civicdataspace.in/privacy-policy-> 307 to /logincivicdataspace.in/privacy-> 200civicdataspace.in/privacy-policy-> 307 to /login/privacywas already the correct, working route on both dev and prod before #472 touched it. This reverts theproxy.tsallowlist entry and the footer link back to/privacy.skip_provider(also from #472) is unrelated and left as-is.