Skip to content
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 plan #1962

Closed
siemvaessen opened this issue Nov 21, 2019 · 4 comments
Closed

Redirect plan #1962

siemvaessen opened this issue Nov 21, 2019 · 4 comments
Assignees
Labels
Dev-ops Devops stuff only
Milestone

Comments

@siemvaessen
Copy link
Member

Review redirect plan by @samuele-mattiuzzo - https://docs.google.com/document/d/1_PihJ6dX__n4spcYiFfuXTV3oC6AE1KeHHxXfKOKu8c/edit

@taufik-hidayat
Copy link
Contributor

Already discussed with @luminhan and also has been made a test in the localhost. The result is working, the next step to implement in the live server.

@siemvaessen
Copy link
Member Author

Ok, the first connection (redirect) test will be performed in the Copenhagen Release.

@samuele-mattiuzzo
Copy link

Any chance you and the team can get in touch with Matt, Mark and the likes to keep coordinating with them on this? @siemvaessen

@andylolz
Copy link
Contributor

You can totally do this in apache, using mod_rewrite, some regex and chaining. However, I think you’re right that it’s going to be better in django middleware.

In case it’s at all useful, I made this tiny flask app that does 302 redirects:
https://v1-iati-datastore.herokuapp.com
Needs updating with new routes, but you get the idea.

@siemvaessen siemvaessen added this to the REDIRECTS milestone Dec 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dev-ops Devops stuff only
Projects
None yet
Development

No branches or pull requests

5 participants