blocks|key|176278|text|尝试在Safari中使用私人浏览或删除整个缓存/cookie。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|176279|我在使用chrome时遇到过一些类似的问题，当时浏览器认为它的缓存中有网站，但实际上并非如此。|176280|使服务器响应A304的http请求的部分是etag。似乎Safari在没有相应缓存的情况下发送了正确的etag。|176281|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Try using private browsing in Safari or deleting your entire cache/cookies.

I've had some similar issues using chrome when the browser thought it had the website in its cache but actually had not.

The part of the http request that makes the server respond a 304 is the etag. Seems like Safari is sending the right etag without having the corresponding cache.

blocks|key|2995013|text|我在Safari和Chrome+(我测试过的唯一的浏览器)中也遇到了同样的问题，但我只是做了一些似乎可以工作的事情，至少自从我添加了解决方案后，我还没有能够重现这个问题。我所做的就是使用生成的时间戳将元标记添加到标头中。看起来不太对，但很简单:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2995014|<meta+name="304workaround"+content="2013-10-24+21:17:23">|code-block|syntax|javascript|2995015|更新+P.S据我所知，当我删除我的节点代理(代理，我指的是express.vhost和http-proxy模块)时，问题就消失了，这很奇怪……|offset|length|style|BOLD|2995016|entityMap^0|0|0|0|2|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I had the same problem in Safari and Chrome (the only ones I've tested) but I just did something that seems to work, at least I haven't been able to reproduce the problem since I added the solution. What I did was add a metatag to the header with a generated timstamp. Doesn't seem right but it's simple :)

<pre><code>&lt;meta name="304workaround" content="2013-10-24 21:17:23"&gt;
</code></pre>

Update
P.S
As far as I can tell, the problem disappears when I remove my node proxy (by proxy i mean both express.vhost and http-proxy module), which is weird...

blocks|key|174314|text|正如您所说，Safari会在重新加载时发送Cache-Control:+max-age=0。Express+(或者更具体地说，Express的依赖项node-fresh)在接收到Cache-Control:+no-cache标头时会考虑缓存过期，但它不会对Cache-Control:+max-age=0执行同样的操作。据我所知，可能应该是这样的。但我不是缓存方面的专家。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|174315|修复方法是将node-fresh/index.js的(当前)第37行从|174316|if+(cc+&&+cc.indexOf('no-cache')+!==+-1)+return+false;++|code-block|syntax|javascript|174317|至|174318|if+(cc+&&+(cc.indexOf('no-cache')+!==+-1+%7C%7C
++cc.indexOf('max-age=0')+!==+-1))+return+false;|174319|我派生了node-fresh和express，通过npm在我的项目的package.json中包含这个修复，你也可以这样做。下面是我的for，例如：|174320|https://github.com/stratusdata/node-fresh+https://github.com/stratusdata/express#safari-reload-fix|174321|safari-reload-fix分支基于3.4.7标记。|174322|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/stratusdata/node-fresh|1|https://github.com/stratusdata/express#safari-reload-fix^0|L|O|2H|N|3K|O|0|6|J|0|0|0|0|P|3|Y|C|0|0|15|0|16|1K|1|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@$9|17|A|18|B|C]|$9|19|A|1A|B|C]|$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1D|8|@$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|1G|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1H|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|1I|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|1J|8|@$9|1K|A|1L|B|C]|$9|1M|A|1N|B|C]]|D|@]|E|$]]|$1|S|3|T|5|6|7|1O|8|@]|D|@$9|1P|A|1Q|1|1R]|$9|1S|A|1T|1|1U]]|E|$]]|$1|U|3|V|5|6|7|1V|8|@]|D|@]|E|$]]|$1|W|3|-4|5|6|7|1W|8|@]|D|@]|E|$]]]|X|$Y|$5|Z|10|11|E|$12|13]]|14|$5|Z|10|11|E|$12|15]]]]

As you said, Safari sends <code>Cache-Control: max-age=0</code> on reload. Express (or more specifically, Express's dependency, node-fresh) considers the cache stale when <code>Cache-Control: no-cache</code> headers are received, but it doesn't do the same for <code>Cache-Control: max-age=0</code>. From what I can tell, it probably should. But I'm not an expert on caching.

The fix is to change (what is currently) line 37 of <code>node-fresh/index.js</code> from

<pre><code>if (cc &amp;&amp; cc.indexOf('no-cache') !== -1) return false; 
</code></pre>

to

<pre><code>if (cc &amp;&amp; (cc.indexOf('no-cache') !== -1 ||
 cc.indexOf('max-age=0') !== -1)) return false;
</code></pre>

I forked node-fresh and express to include this fix in my project's <code>package.json</code> via <code>npm</code>, you could do the same. Here are my forks, for example:

<a href="https://github.com/stratusdata/node-fresh" rel="nofollow noreferrer">https://github.com/stratusdata/node-fresh</a>
<a href="https://github.com/stratusdata/express#safari-reload-fix" rel="nofollow noreferrer">https://github.com/stratusdata/express#safari-reload-fix</a>

The safari-reload-fix branch is based on the 3.4.7 tag.

blocks|key|2995080|text|最简单的解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2995081|app.disable('etag');|code-block|syntax|javascript|2995082|如果您想要更多控制，请在此处提供替代解决方案：|2995083|http://vlasenko.org/2011/10/12/expressconnect-static-set-last-modified-to-now-to-avoid-304-not-modified/|offset|length|2995084|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|2W|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|U|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|V|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|W|8|@]|9|@$K|X|L|Y|1|Z]]|A|$]]|$1|M|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|J]]]]

Easiest solution:

<pre><code>app.disable('etag');
</code></pre>

Alternate solution here if you want more control:

<a href="http://vlasenko.org/2011/10/12/expressconnect-static-set-last-modified-to-now-to-avoid-304-not-modified/">http://vlasenko.org/2011/10/12/expressconnect-static-set-last-modified-to-now-to-avoid-304-not-modified/</a>

blocks|key|175680|text|老问题，我知道。禁用缓存功能是不必要的，也不是管理问题的最佳方法。通过禁用缓存功能，服务器需要更加努力地工作，并产生更多的流量。此外，浏览器和设备需要更加努力地工作，特别是在移动设备上，这可能是一个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|175681|在浏览器中使用Shift+key%2Breload按钮可以轻松地解决空白页面的问题。|175682|空页可能是以下原因造成的：|175683|175684|a+bug+in+your+code+|unordered-list-item|175685|测试时，您提供了一个由浏览器缓存的空页面(您已经记不住了)|175686|+Safari中的一个错误(如果是，请报告给苹果，不要尝试自己修复)|175687|175688|首先尝试Shift键盘键%2B重新加载按钮，看看问题是否仍然存在，并检查您的代码。|175689|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|W|8|@]|9|@]|A|$]]|$1|J|3|K|5|I|7|X|8|@]|9|@]|A|$]]|$1|L|3|M|5|I|7|Y|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

Old question, I know. Disabling the cache facility is not needed and not the best way to manage the problem. By disabling the cache facility the server needs to work harder and generates more traffic. Also the browser and device needs to work harder, especially on mobile devices this could be a problem. 

The empty page can be easily solved by using Shift key+reload button at the browser. 

The empty page can be a result of:

<ul>
<li>a bug in your code </li>
<li>while testing you served an empty page (you can't
remember) that is cached by the browser </li>
<li>a bug in Safari (if so,
please report it to Apple and don't try to fix it yourself)</li>
</ul>

Try first the Shift keyboard key + reload button and see if the problem still exists and review your code.

blocks|key|174345|text|Windows|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|174346|Browser：Chrome|unordered-list-item|174347|
+|174348|操作系统|174349|174350|我使用的是Ctrl+%2B+F5键盘组合。这样做，而不是从缓存中读取，我希望获得一个新的响应。解决方案是硬刷新页面。|174351|在MDN+Web+Docs上|174352|174353|“HTTP304未修改的客户端重定向响应码表明不需要重新传输请求的资源。它是到缓存资源的隐式重定向。”|blockquote|174354|174355|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/304^0|0|7|0|8|6|0|0|0|0|5|9|0|1|C|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|I|3|J|5|6|7|1A|8|@]|D|@]|E|$]]|$1|K|3|L|5|H|7|1B|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|1C|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1D|8|@$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1G|8|@]|D|@$9|1H|A|1I|1|1J]]|E|$]]|$1|R|3|-4|5|6|7|1K|8|@]|D|@]|E|$]]|$1|S|3|T|5|U|7|1L|8|@]|D|@]|E|$]]|$1|V|3|-4|5|6|7|1M|8|@]|D|@]|E|$]]|$1|W|3|-4|5|6|7|1N|8|@]|D|@]|E|$]]]|X|$Y|$5|Z|10|11|E|$12|13]]]]

<ul>
<li>Operating system: <code>Windows</code></li>
<li>Browser: <code>Chrome</code></li>
</ul>
I used <code>Ctrl + F5</code> keyboard combination. By doing so, instead of reading from cache, I wanted to get a new response. The solution is to do hard refresh the page.
On <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/304" rel="nofollow noreferrer">MDN Web Docs</a>:
<blockquote>
&quot;The HTTP 304 Not Modified client redirection response code indicates
that there is no need to retransmit the requested resources. It is an
implicit redirection to a cached resource.&quot;
</blockquote>

blocks|key|175697|text|//+just+add+*+in+URL
++++
app.get('/api*',+(req,+res)=>{

//+do+something+

});|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|175698|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>// just add * in URL
 
app.get('/api*', (req, res)=&gt;{

// do something 

});
</code></pre>

When I reload a website made with express, I get a blank page with Safari (not with Chrome) because the NodeJS server sends me a 304 status code.

How to solve this?

Of course, this could also be just a problem of Safari, but actually it works on all other websites fine, so it has to be a problem on my NodeJS server, too.

To generate the pages, I'm using Jade with <code>res.render</code>.

Update: It seems like this problem occurs because Safari sends <code>'cache-control': 'max-age=0'</code> on reload.

Update 2: I now have a workaround, but is there a better solution?
Workaround:

<pre><code>app.get('/:language(' + content.languageSelector + ')/:page', function (req, res)
{
 // Disable caching for content files
 res.header("Cache-Control", "no-cache, no-store, must-revalidate");
 res.header("Pragma", "no-cache");
 res.header("Expires", 0);

 // rendering stuff here…
}
</code></pre>

Update 3:
So the complete code part is currently:

<pre><code>app.get('/:language(' + content.languageSelector + ')/:page', pageHandle);

function pageHandle (req, res)
{
 var language = req.params.language;
 var thisPage = content.getPage(req.params.page, language);

 if (thisPage)
 {
 // Disable caching for content files
 res.header("Cache-Control", "no-cache, no-store, must-revalidate");
 res.header("Pragma", "no-cache");
 res.header("Expires", 0);

 res.render(thisPage.file + '_' + language, {
 thisPage : thisPage,
 language: language,
 languages: content.languages,
 navigation: content.navigation,
 footerNavigation: content.footerNavigation,
 currentYear: new Date().getFullYear()
 });
 }
 else
 {
 error404Handling(req, res);
 }
}
</code></pre>

NodeJS/express: Cache and 304 status code

服务器

当我重新加载一个用express制作的网站时，我得到一个使用Safari (而不是Chrome)的空白页面，因为NodeJS服务器会给我一个304状态代码。如何解决这个问题？当然，这也可能只是Safari的一个问题，但实际上它在所有其他网站上都可以很好地工作，所以在我的NodeJS服务器上也一定是一个问题。为了生成页面...

问NodeJS/express:缓存和304状态码
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问NodeJS/express:缓存和304状态码EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问NodeJS/express:缓存和304状态码
EN