Get rid of client side redirects #425
Assignees
Labels
Comments
|
#152 is open to test this solution |
|
reopening GitHub auto-closed this because of an old commit being merged e44f5d8 |
|
thank you @thaJeztah! |
|
Fixed in 949a89e |
joaofnfernandes
pushed a commit
to joaofnfernandes/docker.github.io
that referenced
this issue
Nov 11, 2016
- Close docker#194 and fix - Fix and close docker#425 - Fix and close docker#417 - Fix and close docker#420 - Fix and close docker#422 - Adding in documentation build scripts - Fix and close docker#431 - Fix and close docker#438, and Fix and close docker#429 - Work on 441 - Adding in commands reference - Updating all the options to tables - Updating per Vivek docker#498 - Adding vivek's last suggestions Signed-off-by: Mary Anthony <mary@docker.com>
|
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. /lifecycle locked |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Problem description
Current 404 (not found) page is a 240KB JS script that operates client side redirects.
A 6500 lines script that includes all our redirect rules... This script is built using front-matter aliases and what's in
_data/redirects.csv.This should be handled server side.
Suggestions for a fix
@johndmulhausen suggests that we use
redirect_fromwhich Jekyll supports, to generate 301 redirects.The text was updated successfully, but these errors were encountered: