Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1059035

Summary:	[META] Unexpected session errors, should be handled properly
Product:	[Retired] Zanata	Reporter:	Damian Jansen <djansen>
Component:	Component-UI	Assignee:	Carlos Munoz <camunoz>
Status:	CLOSED UPSTREAM	QA Contact:	Zanata-QA Mailling List <zanata-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.2	CC:	aeng, sflaniga, zanata-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-31 01:25:38 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:
Bug Depends On:	1023228
Bug Blocks:

Description Damian Jansen 2014-01-29 03:13:29 UTC

Description of problem:
In many cases, the error page will be along the lines of "You tried to do something but you weren't logged in" or "this broke because you did this".

When this occurs, we should not be showing the "But you can help us fix it" message.
Also, if we know what the error is, and there could be some more information regarding it, then we should display this information or a link to it.

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

How reproducible:
Easy always

Steps to Reproduce:
1. Sign in as admin, go to a project version
2. Press Source Documents, then Upload
3. Select a document to upload, but don't press the Upload button
4. Open the administration page in a new tab, click on Server Monitoring
5. Click Invalidate HTTP Sessions, then OK
6. Go back to the upload tab and press Upload

Actual results:
Your session has timed out. Please try again. 
But you can help us fix it!
[Report Problem]

Expected results:
It should just say Please log in and try again.

Additional info:

Comment 1 Sean Flanigan 2014-01-29 03:32:35 UTC

Could we retitle this to something like "Error pages should offer to log in again if triggered by session timeout"?

Comment 2 Damian Jansen 2014-01-29 05:07:20 UTC

It's a bit more general than that - this is just one isntance of. If it's an error that we expect, like login timeout or multipart upload, we shouldn't offer to fix it for them.

Comment 3 Sean Flanigan 2014-01-29 06:52:13 UTC

Okay, but I think it would help to split each such identified case into its own specific bug, since they will have to be fixed one at a time.

Comment 4 Alex Eng 2014-02-09 21:43:33 UTC

I think generally, if user saw an error page, that would be 'unexpected error' from the server. For this instance, I think we should try to catch this error in the Action handler.

Comment 5 Damian Jansen 2014-07-28 05:55:48 UTC

Turned this into a metabug for session errors

Comment 6 Zanata Migrator 2015-07-31 01:25:38 UTC

Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-497