Cap authorizer POST hangs if any requested cap already exists
Bug #815120 reported by
Chris Osborn
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Sitelier Kernel |
Confirmed
|
Medium
|
Seth Purcell |
Bug Description
If an app requisitions a capability that already exists (or otherwise causes a naming conflict) the resulting authorizer form POST will hang.
This is the result of two distinct problems:
- Re-requesting a cap that has already been granted should not result in a naming conflict, but does.
- A naming conflict error should cause the authorizer POST to fail gracefully rather than hang.
Changed in sitelier-kernel: | |
status: | New → Confirmed |
assignee: | nobody → Seth Purcell (seth-purcell) |
importance: | Undecided → Medium |
To post a comment you must log in.