The response code for a delete call can be any of the following :

 - `DELETE /api/book/122` - The server successfully processed the request, but is not returning any content 
  - `204 No Content`
 - `DELETE /api/book/122` - Resource does not exist 
  - `404 Not Found`
 - `DELETE /api/book/122` - Resource already deleted 
  - `410 Gone`
 - `DELETE /api/book/122` - Users does not have permission
  - `403 Forbidden` 

 - `DELETE /api/book/122` - Method Not Allowed
  - `405 Method Not Allowed`

 - `DELETE /api/book/122` - Conflict (User can resolve the conflict and delete)
  - `409 Conflict`

In your case 404 is apt.

Yes, it would be 404.

In general it will be a 400 series error if the request is wrong somehow, and a 500 series error if something goes awry on the server.


I would suggest taking a look at this flow diagram.  It&#39;s obviously a little bit more than you need but a great resource for future readers.  Sadly there is no excerpt possible.

[http-decision-diagram](https://github.com/for-GET/http-decision-diagram)

[![enter image description here][1]][1]


  [1]: https://i.stack.imgur.com/X46aO.jpg

JAX-RS has annotations for HTTP verbs such as `GET` (`@GET`) and `POST` (`@POST`) but there is no `@PATCH` annotation. How can I have an annotation for the `PATCH` HTTP verb?
 
Something like the following: 

&lt;!-- language: lang-java --&gt;

    @PATCH
    public Response someCode() {
        // Code to handle the request
    }

How to have a @PATCH annotation for JAX-RS?

I&#39;m trying to let the user choose any image that they want on their device to use as a wallpaper in this wallpaper application I&#39;m building. For some reason when I write:

    Intent myIntent = new Intent(Intent.ACTION_PICK);
    myIntent.setType(&quot;image/*&quot;);
    startActivityForResult(myIntent, 100);

I go straight into the gallery, but when I write:

    Intent myIntent = new Intent(Intent.ACTION_GET_CONTENT, null);
    myIntent.setType(&quot;image/*&quot;);
    startActivityForResult(myIntent, 100);

I get to choose from Gallery, or Google Drive. What is the best way to let the user choose what app to retrieve the picture from every time? Or why do those two different intent constants make a difference?

Difference between Intent.ACTION_GET_CONTENT and Intent.ACTION_PICK

I have a resources with uri `/api/books/122` , if this resource doesn&#39;t exist at the point where a client sends HTTP Delete for this resource, what is the appropriate response code from this action? Is it 404 Not Found?    
Thanks

What is the HTTP response code for failed HTTP Delete operation?

<p>I have a resources with uri <code>/api/books/122</code> , if this resource doesn't exist at the point where a client sends HTTP Delete for this resource, what is the appropriate response code from this action? Is it 404 Not Found?<br>
Thanks</p>


From the RFC 2616

http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.1

&gt; no-cache

&gt; If the no-cache directive does not specify a field-name, then a cache
&gt; MUST NOT use the response to satisfy a subsequent request without
&gt; successful revalidation with the origin server. This allows an origin
&gt; server to prevent caching even by caches that have been configured to
&gt; return stale responses to client requests.

So it directs agents to revalidate *all* responses.

Compared this to

&gt; must-revalidate
&gt; 
&gt; When the must-revalidate directive is present in a response received
&gt; by a cache, that cache MUST NOT use the entry after it becomes stale
&gt; to respond to a subsequent request without first revalidating it with
&gt; the origin server

So it directs agents to revalidate *stale* responses.

Particularly with regard to `no-cache`, is this how user agents actually, empirically treat this directive?

What&#39;s the point of `no-cache` if there&#39;s `must-revalidate` and `max-age`?

See this comment:

http://palpapers.plynt.com/issues/2008Jul/cache-control-attributes/

&gt; no-cache
&gt;
&gt; Though this directive sounds like it is instructing the browser not to
&gt; cache the page, there’s a subtle difference. The “no-cache” directive,
&gt; according to the RFC, tells the browser that it should revalidate with
&gt; the server before serving the page from the cache. Revalidation is a
&gt; neat technique that lets the application conserve band-width. If the
&gt; page the browser has cached has not changed, the server just signals
&gt; that to the browser and the page is displayed from the cache. Hence,
&gt; the browser (in theory, at least), stores the page in its cache, but
&gt; displays it only after revalidating with the server. In practice, IE
&gt; and Firefox have started treating the no-cache directive as if it
&gt; instructs the browser not to even cache the page. We started observing
&gt; this behavior about a year ago. We suspect that this change was
&gt; prompted by the widespread (and incorrect) use of this directive to
&gt; prevent caching.

Has anyone got anything more official on this?

*Update*

&gt; The must-revalidate directive ought to be used by servers if and only if failure to validate a request on the representation could result in incorrect operation, such as a silently unexecuted financial transaction.

That&#39;s something I&#39;ve never taken to heart until now. The RFC is saying not to use must-revalidate lightly. The thing is, with web services, you have to take a negative view and assume the worst for your unknown client apps. Any stale resource has the potential to cause a problem.

And something else I&#39;ve just considered, without Last-Modified or ETags, the browser can only fetch the whole resource again. However with ETags, I&#39;ve observed that Chrome at least seems to revalidate on every request. Which makes both these directives moot or at least poorly named since they can&#39;t properly revalidate unless the request also includes other headers that then cause &#39;always revalidate&#39; anyway.

I just want to make that last point clearer. By just setting `must-revalidate` but not including either an ETag or Last-Modified, the agent can only get the content again since it has nothing to send to the server to compare.

However, my empirical testing has shown that when ETag or modified header data is included in responses, the agents always revalidate anyway, regardless of the presence of the `must-revalidate` header.

So the point of `must-revalidate` is to force a &#39;bypass cache&#39; when it goes stale, which can only happen when you have set a lifetime/age, thus if `must-revalidate` is set on a response with no age or other headers, it effectively becomes equivalent to `no-cache` since the response will be considered immediately stale.

-- So I&#39;m going to finally mark Gili&#39;s answer!

Difference between no-cache and must-revalidate

This morning, upon upgrading my Firefox browser to the latest version (from 22 to 23), some of the key aspects of my back office (website) stopped working.

Looking at the Firebug log, the following errors were being reported:

    Blocked loading mixed active content &quot;http://code.jquery.com/ui/1.8.10/themes/smoothness/jquery-ui.css&quot;
    Blocked loading mixed active content &quot;http://ajax.aspnetcdn.com/ajax/jquery.ui/1.8.10/jquery-ui.min.js&quot;`

among other errors caused by the latter of the two above not being loaded.

What does the above mean and how do I resolve it?

Why am I suddenly getting a &quot;Blocked loading mixed active content&quot; issue in Firefox?

Chrome browser by default is blocking mixed content. How do I adjust my settings/configuration to allow mixed content without making any adjustments on the UI every time?

I have found two solutions but neither of them work:

 1. Several articles say you can adjust this under the Security section
    of &quot;Under the Hood&quot; in the Options. This option no longer seems to
    exist. There is no Under The Hood tab and there is no such dropdown
    to adjust how Chrome handles mixed content as far as I can tell.
 2. Another option is to add the `--allow-running-insecure-content` flag
    to your command line. I did this like so:  `&quot;C:\Program
    Files\Google\Chrome\Application\chrome.exe&quot;
    --allow-running-insecure-content`.  However this made no difference. If I tried adding the flag inside the double quotes, then Windows
    complains saying it is invalid.

So what option do I have now with the latest version of Chrome?

How to get Chrome to allow mixed content?

I load some HTML into an iframe but when a file referenced is using http, not https, I get the following error:

&gt; [blocked] The page at {current_pagename} ran insecure content from {referenced_filename}

Is there any way to turn this off or any way to get around it?

The iframe has no `src` attribute and the contents are set using:

    frame.open();
    frame.write(html);
    frame.close();

How to allow http content within an iframe on a https site

I have two questions. I understand that if I specify the domain as `.mydomain.com` (with the leading dot) in the cookie that all subdomains can share a cookie.

Can `subdomain.mydomain.com` access a cookie created in `mydomain.com` (without the `www` subdomain)? 

Can `mydomain.com` (without the `www` subdomain) access the cookie if created in `subdomain.mydomain.com`?

Share cookie between subdomain and domain

I am about to start a project with **AngularJS** for the client side and **Django** for the server side. 

What are the best practices to make them work like best friends (static files,auth, deployment, etc.) 

What are the best practices to use AngularJS with Django

i&#39;ve created a small API using Node/Express and trying to pull data using Angularjs but as my html page is running under apache on localhost:8888 and node API is listen on port 3000, i am getting the No &#39;Access-Control-Allow-Origin&#39;. I tried using  `node-http-proxy` and Vhosts Apache but not having much succes, please see full error and code below. 

&gt;XMLHttpRequest cannot load localhost:3000. No &#39;Access-Control-Allow-Origin&#39; header is present on the requested resource. Origin &#39;localhost:8888&#39; is therefore not allowed access.&quot;    

    // Api Using Node/Express    
    var express = require(&#39;express&#39;);
	var app = express();
	var contractors = [
	    {   
	     &quot;id&quot;: &quot;1&quot;, 
	        &quot;name&quot;: &quot;Joe Blogg&quot;,
	        &quot;Weeks&quot;: 3,
	        &quot;Photo&quot;: &quot;1.png&quot;
	    }
	];

	app.use(express.bodyParser());

	app.get(&#39;/&#39;, function(req, res) {
	  res.json(contractors);
	});
	app.listen(process.env.PORT || 3000);
	console.log(&#39;Server is running on Port 3000&#39;)
        

##Angular code

    angular.module(&#39;contractorsApp&#39;, [])
    .controller(&#39;ContractorsCtrl&#39;, function($scope, $http,$routeParams) {

       $http.get(&#39;localhost:3000&#39;).then(function(response) {
           var data = response.data;
           $scope.contractors = data;
       })
     
##HTML

    &lt;body ng-app=&quot;contractorsApp&quot;&gt;
		&lt;div ng-controller=&quot;ContractorsCtrl&quot;&gt; 
			&lt;ul&gt;
			    &lt;li ng-repeat=&quot;person in contractors&quot;&gt;{{person.name}}&lt;/li&gt;
			&lt;/ul&gt;
		&lt;/div&gt;
	&lt;/body&gt;

No &#39;Access-Control-Allow-Origin&#39; - Node / Apache Port Issue

I want to serialize a model, but want to include an additional field that requires doing some database lookups on the model instance to be serialized:

    class FooSerializer(serializers.ModelSerializer):
      my_field = ... # result of some database queries on the input Foo object
      class Meta:
            model = Foo
            fields = (&#39;id&#39;, &#39;name&#39;, &#39;myfield&#39;)

What is the right way to do this? I see that [you can pass in extra &quot;context&quot;][1] to the serializer, is the right answer to pass in the additional field in a context dictionary? 

With that approach, the logic of getting the field I need would not be self-contained with the serializer definition, which is ideal since every serialized instance will need `my_field`. Elsewhere in the DRF serializers documentation it [says][2] &quot;extra fields can correspond to any property or callable on the model&quot;. Are &quot;extra fields&quot; what I&#39;m talking about? 

Should I define a function in `Foo`&#39;s model definition that returns `my_field` value, and in the serializer I hook up my_field to that callable? What does that look like?

Happy to clarify the question if necessary. 


  [1]: http://www.django-rest-framework.org/api-guide/serializers/#including-extra-context
  [2]: http://django-rest-framework.org/api-guide/serializers.html#specifying-fields-explicitly

Django REST Framework: adding additional field to ModelSerializer

I keep a key-value storage in the server for the client. If the user sends key &quot;k1&quot;, then I upsert it to the database. Is this considered `POST` or `PUT`?

Also I have another operation that removes all existing keys and adds the new key. Is this `POST` or `PUT` because it clears records and adds a new one.

In REST is POST or PUT best suited for upsert operation?

I am trying to understand the Backbone.js sync method and was going through the documentation on 
http://backbonejs.org/#Sync

It says

    The default sync handler maps CRUD to REST like so:
    
    create → POST   /collection
    read → GET   /collection[/id]
    update → PUT   /collection/id
    delete → DELETE   /collection/id

Now since I have always been in front-end development and new to Backbone, I find the above hard to understand...I have never used REST or any other server-side protocols...

Could you please explain the same in simple terms (like how the REST maps when we use Backbone.sync)
Any very simple example would be highly useful...

Content Type	Original Author	Original Content on Stackoverflow
Question	KlsLondon	View Question on Stackoverflow
Solution 1 - Http	George John	View Answer on Stackoverflow
Solution 2 - Http	Will Hartung	View Answer on Stackoverflow
Solution 3 - Http	Erik Philips	View Answer on Stackoverflow

What is the HTTP response code for failed HTTP Delete operation?

Http Problem Overview

Http Solutions

Solution 1 - Http

Solution 2 - Http

Solution 3 - Http

Difference between Intent.ACTION_GET_CONTENT and Intent.ACTION_PICK

How to have a @PATCH annotation for JAX-RS?

Attributions