Task #8385 (closed)
Opened 12 years ago
Closed 12 years ago
403 with POST page
| Reported by: | wmoore | Owned by: | wmoore |
|---|---|---|---|
| Priority: | major | Milestone: | OMERO-4.4 |
| Component: | Web | Version: | n.a. |
| Keywords: | n.a. | Cc: | atarkowska, cxallan |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
Currently the Ajax Error handling calls refresh if we get a 403 (timeout etc) which will redirect to login page, then back to current location on login.
A side effect of this on pages such as Search where you have arrived with a POST, is the browser will ask you to confirm you want to POST data again, before taking you to the login page and back to Search page, with the POST data missing.
Not sure whether there's a nice way to handle this, or if we want to change the 403 handling, or just ignore??
Change History (1)
comment:1 Changed 12 years ago by wmoore
- Resolution set to wontfix
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
I think we can ignore this, since it is very much an edge case, especially if timeout is rare.