Databases
StackOverflow2013
Postsdbo
POChrome is caching an HTTP PUT request
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POChrome is caching an HTTP PUT request
    primarykey
    data
    text
    <p>I have this bizarre issue with Chrome. It quite often appears to cache PUT requests.</p> <p><strong>The Details:</strong> I have an app using backbone.js and when trying to persist some changes to a model (backbone automatically generates a PUT request), Chrome just wont send that request to the server. It works perfectly fine in Firefox and IE (haven't seen the issue in Safari so far).</p> <p>Here's a screenshot from the Chrome developer tools' Network tab. As you can see, the response for the PUT request is being returned from cache (the request doesn't hit the server!!) <img src="https://i.stack.imgur.com/p4RQt.png" alt="Chrome caches PUT request"></p> <p>Here's a screenshot of the header details of that same request. Once again, it's evident that Chrome doesn't bother sending the PUT request to the server. <img src="https://i.stack.imgur.com/FL2F3.png" alt="Chrome cached PUT request header"></p> <p>The payload of the request is JSON data. Any thoughts as to why this is happening / what I'm doing wrong?</p> <p><strong>UPDATE:</strong> Chromium has confirmed that this is indeed a <a href="http://code.google.com/p/chromium/issues/detail?id=136320" rel="noreferrer">bug on it's end</a> (thanks Jan Hančič).</p> <p><strong>TEMPORARY SOLUTION</strong> I ended up overriding <code>Backbone.sync</code> method and appending a timestamp to the querystring of PUT, POST and DELETE requests so that they are always unique:</p> <pre><code>if(!options.data &amp;&amp; model &amp;&amp; (method == 'create' || method == 'update' || method == 'delete')) { params.url += (params.url.indexOf('?') == -1 ? '?' : '&amp;') + '_=' + new Date().getTime(); } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USanushr
    1. USanushr
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POChrome is caching an HTTP PUT request
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POChrome is caching an HTTP PUT request
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POChrome is caching an HTTP PUT request
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODoes this only happen if you send data in the PUT request, that you'll already send before or does this also occure if you change the data to be submitted and trigger the request again?
      singulars
      1. POChrome is caching an HTTP PUT request
      1. USRobin Drexler
    2. COThe response from the server doesn't change maybe that's why its cached. Like Robin said, change/correct the request
      singulars
      1. POChrome is caching an HTTP PUT request
      1. USZebra
    3. COThe data definitely changes. However, I would think that it shouldn't matter whether the data has changed or not. A PUT really isn't a cacheable request type. It's meant to send data to the server, not fetch data.
      singulars
      1. POChrome is caching an HTTP PUT request
      1. USanushr
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload