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

Add HTTP 302 redirection via .htaccess #9

Open
k3rs3d opened this issue Jul 5, 2024 · 0 comments
Open

Add HTTP 302 redirection via .htaccess #9

k3rs3d opened this issue Jul 5, 2024 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@k3rs3d
Copy link
Owner

k3rs3d commented Jul 5, 2024

(Idea from Eamon - @eamon@social.coop - https://git.eamoncaddigan.net/)

We can generate/modify a .htaccess file to make a web server redirect pages instead of making the visitor's browser do the redirecting. This would be more efficient but would require the webring admin to have control over the web server (ie probably self-hosted, not hosted on a service like Neocities or GH Pages).
So for example the server itself would redirect visitors to example.com/slug/next/ to the proper site in the ring's sequence. Visitors would never load a page from example.com/slug/next (which is how ringfairy currently works)
So, ringfairy should have a config option to enable/disable generating/modifying a .htaccess file. By default this should be disabled.

@k3rs3d k3rs3d added enhancement New feature or request help wanted Extra attention is needed good first issue Good for newcomers labels Jul 5, 2024
@k3rs3d k3rs3d changed the title HTTP 302 redirection vs .htaccess Add HTTP 302 redirection via .htaccess Jul 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant