|Summary:||report should not display http headers to users|
|Product:||Red Hat Enterprise Linux 6||Reporter:||Andrew Hecox <ahecox>|
|Component:||report||Assignee:||Gavin Romig-Koch <gavin>|
|Status:||CLOSED CURRENTRELEASE||QA Contact:||David Kutálek <dkutalek>|
|Version:||6.0||CC:||borgan, dkutalek, snagar|
|Fixed In Version:||report-0.18-6||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2010-11-10 21:29:51 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Andrew Hecox 2010-08-04 20:01:31 UTC
Created attachment 436650 [details] case creation failing report currently displays the http headers in it's GTK screens to the customers. See attached screenshots.
Comment 1 Andrew Hecox 2010-08-04 20:01:51 UTC
Created attachment 436651 [details] case creation succeeding
Comment 2 Andrew Hecox 2010-08-04 20:02:43 UTC
Sly / Denise -- this is a very easy fix for us which I'd like to get in if possible. It's very ugly in the GTK screens for report users, eg, selinux.
Comment 3 Andrew Hecox 2010-08-04 20:03:15 UTC
for the failure case, we should just display the message returned; for the success case, we should just say "thank you" and a reference to the newly created case in the portal.
Comment 4 Gavin Romig-Koch 2010-08-11 13:18:02 UTC
In the end the safest change to accomplish this was just to not print out anything except the messages that the server sent for cases of success (http response codes 200 and 201) and user errror (400<=x<500). For server error response codes (500 <= x < 600) we print out as much info as we have. This means that to fully fix this we will need the server to improve the messages it sends. This is in progress. Someone, likely me, who knows what messages the server is sending will have to verify this bug.
Comment 6 David Kutálek 2010-08-18 16:08:35 UTC
Created attachment 439432 [details] QA - server messages in report gui after moving bug to ON_QA
Comment 8 firstname.lastname@example.org 2010-11-10 21:29:51 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you.