Context-aware 404 page (BB-2146)

Fabian Kraemer avatarFabian Kraemer created an issue

E.g. requesting auiplugin-3.6.4 - /src/doesnotexist responds with a 404, but what the application could do is recognise that the request is to a sub-path (after the cs hash) and then try to match the path upwards, e.g. auiplugin/src and then auiplugin and then 27619acd21da. The user then gets redirected to that path instead of a 404. The page should have a warning message that this is not the originally requested resource but the closest the application could match.

Comments (8)

  1. Fabian Kraemer
    • changed status to open

    I can follow your argumentation and agree with it. What do you think of providing this functionality (asynchronously) on the 404 page (specialised only for that resource requests)? Sth. like "Can't find the requested resource on branch x, did you mean? ...

  2. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.