-
Notifications
You must be signed in to change notification settings - Fork 449
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
Fix redirect rules and drop misnamed and misplaced _redirects files #668
Comments
@tomkerkhove - as was mentioned in the opening comment, the following rules aren't being processed by Netlify: Lines 1 to 4 in edde5ff
Some of these are encoded in the layouts/index.redirects, but not all. Do you need these rules? Also note that the
/cc @nate-double-u /tag cleanup |
Yes, we need those indeed but these should work normally; for example if you go to But I'm not sure if it's that or because of the versions. If I recall correctly these were there for our old docs, but not a must from my side. Thoughts @kedacore/keda-maintainers? |
+1 |
FYI, https://github.com/kedacore/keda-docs/blob/main/static/_redirects get overwritten by the generated file of the same name. All rules have an equivalent in the generated file except for this redirect: $ curl -s -D - -o /dev/null https://keda.sh/concepts/overview
HTTP/2 404 Just to be clear: so you'd like me to add a rule for |
I'd say ensure we have rules for all of these: Lines 1 to 4 in edde5ff
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
Bump |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to inactivity. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to inactivity. |
Is this solved? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
Is this solved? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to inactivity. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to inactivity. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
should we mark this as ignored for stale bot? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to inactivity. |
Redirect rules should be defined in layouts/index.redirects.
The following two files should be deleted. We might need to ensure that their rules are covered first thought:
/concepts/overview
rule (all other rule are covered by the generated redirects file).301!
rule qualifiersThe text was updated successfully, but these errors were encountered: