Bug 1614171

Summary: Beaker does not give a 404 error if you try to access the URL of a non-existent task
Product: [Retired] Beaker Reporter: Dan Callaghan <dcallagh>
Component: web UIAssignee: Tomas Klohna 🔧 <tklohna>
Status: CLOSED NEXTRELEASE QA Contact: tools-bugs <tools-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 25CC: mastyk, tklohna
Target Milestone: 26.3Keywords: EasyFix, Patch
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-14 08:50:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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.