| Summary: | [user] Better usability on 403 pages | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | John J. Barton <johnjbarton> | ||||
| Component: | Server | Assignee: | Malgorzata Janczarska <malgorzata.tomczyk> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | ahunter.eclipse, simon_kaegi, Szymon.Brandys | ||||
| Version: | 0.2 | ||||||
| Target Milestone: | 0.2 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
It is not only html calls. I would also improve xhr calls handling. The change is released to branch bug33038. I had to use authentication service to generate the 403 error. In displays error information and login form. To get 403 in html (plain) call 1. login 2. go to <host>/users/B (or whatever is not your user URI) <host>/workspace/C (or whatever is not your workspace) etc. This is all about plain HTML calls, not the ones made from out client in dojo. Created attachment 205659 [details]
screenshoot
I'm not sure if this is a good solution. Moving to 0.4 hoping to get others opinion. (In reply to Malgorzata Janczarska from comment #4) > I'm not sure if this is a good solution. Moving to 0.4 hoping to get others > opinion. The 403 error says: You are not authorized to access /workspace/{user}-OrionContent I agree this is sufficient. |
The current 403 page is ------------- HTTP ERROR 403 Problem accessing /file/A/extensions/dyne/branches/dyne0.1/doc/index.html. Reason: FORBIDDEN Powered by Jetty:// ------------- The page should: tell you what user-id you are currently using (eg openid johnjbarton) explain that the user-id for the requested page does not match link to the login and to the navigator page