| Anonymous | Login | 2024-12-22 00:10 MST |
| Main | My View | View Issues | Change Log | Roadmap | Repositories |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0022461 | ClearOS | clearos-framework | public | 2018-11-21 10:33 | 2019-02-23 16:27 | ||||
| Reporter | user2 | ||||||||
| Assigned To | dloper | ||||||||
| Priority | normal | Severity | feature | Reproducibility | have not tried | ||||
| Status | closed | Resolution | suspended | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | |||||||||
| Target Version | 7.6.0 Updates | Fixed in Version | |||||||
| Summary | 0022461: Add new standard Exceptions/REST responses | ||||||||
| Description | There will be some circumstances where an API request will need to send a "not capable" error message. Consider the case of updating a user's profile: - REST: POST /api/v1/user/cindy - API: user->update() If using the Active Directory connector, no updates/writes are allowed for users -- AD handles that. The REST response and exception should return this standard "not capable" error. Clients can then handle the specific issue if desired. | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
|
(0009581) dloper (administrator) 2019-02-23 16:27 |
Migrated to: https://gitlab.com/clearos/clearfoundation/clearos-framework/issues/2 [^] |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2018-11-21 10:33 | user2 | New Issue | |
| 2018-11-21 10:34 | user2 | Status | new => confirmed |
| 2019-02-23 16:27 | dloper | Note Added: 0009581 | |
| 2019-02-23 16:27 | dloper | Status | confirmed => closed |
| 2019-02-23 16:27 | dloper | Assigned To | => dloper |
| 2019-02-23 16:27 | dloper | Resolution | open => suspended |
|
Issue History |