Bug 1614171 - Beaker does not give a 404 error if you try to access the URL of a non-existent task
Summary: Beaker does not give a 404 error if you try to access the URL of a non-existe...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: web UI
Version: 25
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: 26.3
Assignee: Tomas Klohna 🔧
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-09 06:40 UTC by Dan Callaghan
Modified: 2019-01-28 10:08 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-01-14 08:50:06 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Beaker Project Gerrit 6383 0 None None None 2019-01-10 13:13:18 UTC

Description Dan Callaghan 2018-08-09 06:40:35 UTC
Description of problem:


Version-Release number of selected component (if applicable):
25.6

How reproducible:
easily

Steps to Reproduce:
1. Click https://$YOURBEAKER/tasks/no/such/task

Actual results:
You just get a 302 redirect back to /tasks with no error message.

Expected results:
Response code should be a 404, there should be an error message

Additional info:
Historically a lot of old TG pages would redirect somewhere with a flash message saying "No such blah" instead of just giving a plain 404 with a sensible error message. Most likely this code is trying to do that but since /tasks is not use Turbogears anymore the flash message is not shown.

In general we should be switching towards the more conventional (and semantic) response of 404 with a good error, instead of redirecting with flash messages.

Comment 1 Martin Styk 2019-01-28 10:08:19 UTC
Beaker 26.3 has been released.


Note You need to log in before you can comment on or make changes to this bug.