You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There should be redirects. While a page based redirect could forward to the overview, a JavaScript based approach could analyze the anchor and then direct to the right page in the new securing guide.
How to Reproduce?
Open the old link.
Anything else?
Having a JavaScript based approach on the 404 page would provide a better response code to automatic crawlers compared to 200 with a meta redirect. AFAIK no other redirect techniques exist for GitHub pages.
Additional thoughts: IMHO JavaScript based redirects is the way, as it can also handle removed (JavaDoc) API docs to redirect to the latest.
ahus1
changed the title
Users hit a 404 when they try to access the old security apps guide
Users hit a 404 when they try to access the old securing apps guide
Jan 30, 2025
Related to #559
Signed-off-by: stianst <stianst@gmail.com>
Signed-off-by: Alexander Schwartz <aschwart@redhat.com>
Co-authored-by: Alexander Schwartz <aschwart@redhat.com>
Describe the problem
A lot of external pages link to and see a 404 page:
It seems that ~200 users per day are affected.
Similar to that it happens for this older guide:
It seems that ~50 users per day are affected.
Expected behavior
There should be redirects. While a page based redirect could forward to the overview, a JavaScript based approach could analyze the anchor and then direct to the right page in the new securing guide.
How to Reproduce?
Open the old link.
Anything else?
Having a JavaScript based approach on the 404 page would provide a better response code to automatic crawlers compared to 200 with a meta redirect. AFAIK no other redirect techniques exist for GitHub pages.
A 404 page where to add the necessary JavaScript is now available here: https://github.com/keycloak/keycloak-web/blob/main/pages/404.ftl
It should be simple to add new redirect to the page with and without a hash/anchor.
The text was updated successfully, but these errors were encountered: