This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
$resource obj.$delete sends the resource as the request body #4280
Comments
bourey
added a commit
to bourey/angular.js
that referenced
this issue
Oct 4, 2013
Prevent the obj.$delete instance method from sending the resource as the request body. This commit uses the existing hasBody boolean to only set httpConfig.data for methods which should have a request body. Closes angular#4280
jeffbcross
pushed a commit
to jeffbcross/angular.js
that referenced
this issue
Oct 4, 2013
Prevent the obj.$delete instance method from sending the resource as the request body. This commit uses the existing hasBody boolean to only set httpConfig.data for methods which should have a request body. Closes angular#4280
jamesdaily
pushed a commit
to jamesdaily/angular.js
that referenced
this issue
Jan 27, 2014
Prevent the obj.$delete instance method from sending the resource as the request body. This commit uses the existing hasBody boolean to only set httpConfig.data for methods which should have a request body. Closes angular#4280
jamesdaily
pushed a commit
to jamesdaily/angular.js
that referenced
this issue
Jan 27, 2014
Prevent the obj.$delete instance method from sending the resource as the request body. This commit uses the existing hasBody boolean to only set httpConfig.data for methods which should have a request body. Closes angular#4280
This was referenced Nov 25, 2014
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Angular's
$resourcedelete method sends the resource as the request body. This behavior is a change from angular1.0.x, and appears to contradict the intention articulated in #3207.This issues specifically affects the
obj.$deleteinstance action and is not demonstrated via$resource.delete.The text was updated successfully, but these errors were encountered: