Status: Resolved (View Workflow)
Affects Version/s: 0.7.0
Fix Version/s: 0.8.1
Git Pull Request:
Similar Issues:Show 10 results
AGPUSH-438 Installations cannot be deleted AGPUSH-614 Update UnifiedPushClient examples with updated pushServer URL and code AGPUSH-170 AeroDoc backend: make PushServer details configurable AGPUSH-137 Push: REST Endpoints: User management AGPUSH-158 Backend: Port AeroDoc to work against MASTER AGPUSH-160 SimplePush: Port AeroDoc to work against MASTER AGPUSH-63 UnifiedPush: Specifications AGPUSH-58 Proper REST support AGPUSH-59 REST: Secure the endpoints AGPUSH-57 UnifiedPush: RESTful endpoints
According to http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.7, DELETE method should identify resource to be deleted by Resource-URI.
Methods should not require a application/json formatted body. Note that clients are not so strict here, but some of them simply turn request to POST if body is present. Some of them does not allow DELETE to include a body.
Current API also duplicates data, for instance pushApplicationID is both part of URI and JSON body.
More discussions about topic here:
I'm marking issue as critical as it affects API we are trying to stabilize.