http-status-code-304

问题 I build a service worker which always responds with data from the cache and then, in the background, sends a request to the server. If the server responds with HTTP 304 - not modified everything is fine, if the server responds with HTTP 200 , that means the data was changed and the new file is put into the cache, also the user is notified and asked for a page refresh. I use the not-modified-since / last-modified headers to make sure the client gets the most up-to-date version. When a request

问题 When a web server responds to HttpWebRequest.GetResponse() with HTTP 304 (Not Modified), GetResponse() thows a WebException , which is so very weird to me. Is this by design or am I missing something obvious here? 回答1: Ok, this seems to be a by-design behavior and a perfect example of a vexing exception. This can be solved with this: public static HttpWebResponse GetHttpResponse(this HttpWebRequest request) { try { return (HttpWebResponse) request.GetResponse(); } catch (WebException ex) { if

问题 When a web server responds to HttpWebRequest.GetResponse() with HTTP 304 (Not Modified), GetResponse() thows a WebException , which is so very weird to me. Is this by design or am I missing something obvious here? 回答1: Ok, this seems to be a by-design behavior and a perfect example of a vexing exception. This can be solved with this: public static HttpWebResponse GetHttpResponse(this HttpWebRequest request) { try { return (HttpWebResponse) request.GetResponse(); } catch (WebException ex) { if

问题 Code Igniter version '2.0.3' Jquery 1.7 Jquery History plugin Hi guys, I have a CodeIgniter app that I've built in an ajax fashion. I have a function as follows: $(document).on('click','.ajax_link',function(e){ //Stop the normal href action e.preventDefault(); //Grab the destination URL var new_url = $(this).attr('href') //Grab the content via ajax and pass it to the history change function $.get(base_url+new_url,function(data){ History.pushState({ content:data.content, url:data.url }, data

问题 Sorry for the probably wrong title. I am writing some code to handle If-Modified-Since and If-None-Match requests as part of caching. Everything works perfect except for that PHP returns some content (an empty line) after the headers. The page content should be empty instead. The code that I am using is: <?php $lastmod = filemtime($f); $etag = '"'.dechex($lastmod).'"'; if ($_SERVER['HTTP_IF_MODIFIED_SINCE'] == $last_mod || $_SERVER['HTTP_IF_NONE_MATCH'] == $etag) { header('HTTP/1.1 304 Not

问题 I am making an Ajax.request to a backend I don't control. This request sometimes redirects me to the login page, and my response.status is 200 instead of 302. So far I have tried this: Ext.Ajax.on("requestexception", function(conn, response, options, eOpts){ console.log(conn); console.log(response); console.log(options); console.log(eOpts); }); Ext.Ajax.request({ url : 'someUrl' params : params }); Obviously this redirection is not what I expected so I need to spot when a 304 happened. There

问题 I am newbie to ruby and rails for several months now.I took a class for ruby and rails which allowed me to create a restaurant blog site. Well I recently started revamping the site to make for my friend. So it's merely just changing some things around pictures, wording, etc. When I created the other blog completely I made a register to log in page which they need to create a log in in order to create and post a comment etc. Everything seems to work fine when I run rails s for the local host

问题 I'm trying to disable all the caches in nginx for testing purpose. I've set the following line add_header Cache-Control no-cache; I see that the page itself is not cached, but the images, css, and javascripts are. I suspect that this is because Firefox is getting "304 Not Modified" header. Is there a way to prevent it? P.S: I think I found it myself. Firefox shows '200 OK' all the time now. Is this correct way? I've added if_modified_since off; add_header Last-Modified ""; 回答1: Sounds right

问题 Is it an ExpiresDefault Apache directive enough to avoid HTTP Status 304 responses from the server? I have set ExpiresDefault "access plus 10 years" but I'm still seeing log entries with a 304 response for "GET /assets/template/default/css/style.min.css?v=1 HTTP/1.1" whenever I open any page on a local PHPMyFAQ site. Emptying the browser cache doesn't seem to change anything. 回答1: The Expires: header your server sends out has nothing to do with future 304 responses. It provides only an

问题 When I send a 304 response. How will the browser interpret other headers which I send together with the 304? E.g. header("HTTP/1.1 304 Not Modified"); header("Expires: " . gmdate("D, d M Y H:i:s", time() + $offset) . " GMT"); Will this make sure the browser will not send another conditional GET request (nor any request) until $offset time has "run out"? Also, what about other headers? Should I send headers like this together with the 304: header('Content-Type: text/html'); Do I have to send: