blocks|key|3129062|text|试着将一些东西存储到cookie中，然后阅读它。如果你没有得到你想要的，那么cookies可能被禁用了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3129063|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Try to store something into a cookie, and then read it. If you don't get what you expect, then cookies are probably disabled.

blocks|key|350637|text|发送设置了cookie的重定向响应；在处理cookie的(特殊)重定向URL测试时-如果存在，则重定向到正常处理，否则重定向到错误状态。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|350638|请注意，这只能告诉您浏览器允许设置cookie，而不是设置多长时间。我的FF允许我强制所有的cookies到“会话”模式，除非站点被特别添加到一个例外列表中-当FF关闭时，这样的cookies将被丢弃，而不管服务器指定的过期时间。这就是我总是运行FF的模式。|350639|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Send a redirect response with the cookie set; when processing the (special) redirected URL test for the cookie - if it's there redirect to normal processing, otherwise redirect to an error state.

Note that this can only tell you the browser permitted the cookie to be set, but not for how long. My FF allows me to force all cookies to "session" mode, unless the site is specifically added to an exception list - such cookies will be discarded when FF shuts down regardless of the server specified expiry. And this is the mode I run FF in always.

blocks|key|350681|text|我不认为有直接的方法来检查。最好的方法是在cookie中存储一个值，并尝试读取它们，然后决定是否启用cookie。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|350682|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I dont think there are direct ways to check. The best way is to store a value in the cookie and try to read them and decide whether cookies are enabled or not.

blocks|key|3342142|text|您可以使用Javascript来完成此任务|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3342143|库：|offset|length|style|BOLD|3342144|function+createCookie(name,+value,+days)+{
++++var+expires;
++++if+(days)+{
++++++++var+date+=+new+Date();
++++++++date.setTime(date.getTime()+%2B+(days+*+24+*+60+*+60+*+1000));
++++++++expires+=+";+expires="+%2B+date.toGMTString();
++++}
++++else+expires+=+"";
++++document.cookie+=+name+%2B+"="+%2B+value+%2B+expires+%2B+";+path=/";
}

function+readCookie(name)+{
++++var+nameEQ+=+name+%2B+"=";
++++var+ca+=+document.cookie.split(';');
++++for+(var+i+=+0;+i+<+ca.length;+i%2B%2B)+{
++++++++var+c+=+ca[i];
++++++++while+(c.charAt(0)+==+'+')+c+=+c.substring(1,+c.length);
++++++++if+(c.indexOf(nameEQ)+==+0)+return+c.substring(nameEQ.length,+c.length);
++++}
++++return+null;
}

function+eraseCookie(name)+{
++++createCookie(name,+"",+-1);
}

function+areCookiesEnabled()+{
++++var+r+=+false;
++++createCookie("testing",+"Hello",+1);
++++if+(readCookie("testing")+!=+null)+{
++++++++r+=+true;
++++++++eraseCookie("testing");
++++}
++++return+r;
}|code-block|syntax|javascript|3342145|要运行的代码：|3342146|alert(areCookiesEnabled());|3342147|记住|3342148|这只有在Javascript被启用的情况下才能起作用！|3342149|entityMap^0|0|0|2|0|0|4|3|0|0|0|2|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|10|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|11|8|@$D|12|E|13|F|G]]|9|@]|A|$]]|$1|O|3|P|5|J|7|14|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|15|8|@$D|16|E|17|F|G]]|9|@]|A|$]]|$1|S|3|T|5|6|7|18|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|V|$]]

You can use Javascript to accomplish that

Library:

<pre class="lang-js prettyprint-override"><code>function createCookie(name, value, days) {
 var expires;
 if (days) {
 var date = new Date();
 date.setTime(date.getTime() + (days * 24 * 60 * 60 * 1000));
 expires = "; expires=" + date.toGMTString();
 }
 else expires = "";
 document.cookie = name + "=" + value + expires + "; path=/";
}

function readCookie(name) {
 var nameEQ = name + "=";
 var ca = document.cookie.split(';');
 for (var i = 0; i &lt; ca.length; i++) {
 var c = ca[i];
 while (c.charAt(0) == ' ') c = c.substring(1, c.length);
 if (c.indexOf(nameEQ) == 0) return c.substring(nameEQ.length, c.length);
 }
 return null;
}

function eraseCookie(name) {
 createCookie(name, "", -1);
}

function areCookiesEnabled() {
 var r = false;
 createCookie("testing", "Hello", 1);
 if (readCookie("testing") != null) {
 r = true;
 eraseCookie("testing");
 }
 return r;
}
</code></pre>

Code to run:

<pre class="lang-js prettyprint-override"><code>alert(areCookiesEnabled());
</code></pre>

Remember

This only works if Javascript is enabled!

blocks|key|349671|text|cookies是否“启用”的问题过于简单。我的浏览器(Opera)有一个每个站点的cookie设置。此外，该设置不是yes/no。实际上，最有用的形式是“仅会话”，忽略服务器的到期日期。如果您在设置后直接测试它，它将在那里。明天，就不会了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|349672|此外，因为它是一个可以更改的设置，所以即使测试cookie是否仍然存在，也只能在测试时告诉您该设置。我可能已经决定手动接受这一块饼干。如果我一直收到垃圾邮件，我可以(有时也会)关闭该站点的cookies。|349673|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The question whether cookies are "enabled" is too boolean. My browser (Opera) has a per-site cookie setting. Furthermore, that setting is not yes/no. The most useful form is in fact "session-only", ignoring the servers' expiry date. If you test it directly after setting, it will be there. Tomorrow, it won't.

Also, since it's a setting you can change, even testing whether cookies do remain only tells you about the setting when you tested. I might have decided to accept that one cookie, manually. If I keep being spammed, I can (and at times, will) just turn off cookies for that site.

blocks|key|3129262|text|检查cookie支持的一种常见方法是通过重定向。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3129263|最好仅在用户尝试执行启动会话的操作时执行此操作，例如登录或向购物车添加内容。否则，根据您的处理方式，您可能会阻止不支持cookies的用户或机器人访问整个站点。|3129264|首先，服务器会照常检查登录数据--如果登录数据有误，用户会照常收到反馈。如果它是正确的，那么服务器立即响应一个cookie，并重定向到一个旨在检查该cookie的页面-这可能只是相同的URL，但在查询字符串中添加了一些标记。如果第二个页面没有收到cookie，则用户会收到一条消息，说明他们无法登录，因为浏览器上禁用了cookie。|3129265|如果您已经在登录表单中遵循Post-+redirect+-Get模式，则此cookie的设置和检查不会添加任何额外的请求-+cookie可以在现有重定向期间设置，并由重定向后加载的目标进行检查。|3129266|现在来解释为什么我只在用户启动的操作之后而不是在每次页面加载时执行cookie测试。我见过网站在每个页面上都实现了cookie测试，但没有意识到这会对搜索引擎试图抓取网站的事情产生影响。也就是说，如果用户启用了cookie，那么测试cookie将被设置一次，因此他们只需在请求的第一个页面上经历重定向，从那时起就没有重定向了。但是，对于任何不返回cookie的浏览器或其他用户代理，例如搜索引擎，每个页面都可能导致重定向。|3129267|另一种检查cookie支持的方法是使用Javascript+-这样，不一定需要重定向-您可以编写cookie并几乎立即读回它，以查看它是否被存储然后检索。这样做的缺点是它在客户端的脚本中运行-如果你仍然想要关于是否支持cookie返回服务器的消息，那么你仍然必须组织它-例如通过Ajax调用。|3129268|对于我自己的应用程序，我通过在用户登录之前在登录屏幕上设置一个包含随机令牌的cookie，并在用户提交他们的登录详细信息时检查该令牌，来实现对“login+CSRF”攻击的一些保护。从Google获取更多关于Login+CSRF的信息。这样做的一个副作用是，当他们登录时，我可以检查该cookie是否存在-不需要额外的重定向。|3129269|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

A common way of checking for cookie support is via a redirect.

It's a good idea to only do this when the user is trying to do something that initiates a session, such as logging in, or adding something to their cart. Otherwise, depending on how you handle it, you're potentially blocking access to your entire site for users - or bots - that don't support cookies.

First, the server checks the login data as normal - if the login data is wrong the user receives that feedback as normal. If it's right, then the server immediately responds with a cookie and a redirect to a page which is designed to check for that cookie - which may just be the same URL but with some flag added to the query string. If that second page doesn't receive the cookie, then the user receives a message stating that they cannot log in because cookies are disabled on their browser.

If you're following the Post-Redirect-Get pattern for your login form already, then this setting and checking of the cookie does not add any additional requests - the cookie can be set during the existing redirect, and checked by the destination that loads after the redirect.

Now for why I only do a cookie test after a user-initiated action other than on every page load. I have seen sites implement a cookie test on every single page, not realising that this is going to have effects on things like search engines trying to crawl the site. That is, if a user has cookies enabled, then the test cookie is set once, so they only have to endure a redirect on the first page they request and from then on there are no redirects. However, for any browser or other user-agent, like a search engine, that doesn't return cookies, every single page could simply result in a redirect.

Another method of checking for cookie support is with Javascript - this way, no redirect is necessarily needed - you can write a cookie and read it back virtually immediately to see if it was stored and then retrieved. The downside to this is it runs in script on the client side - ie if you still want the message about whether cookies are supported to get back to the server, then you still have to organise that - such as with an Ajax call.

For my own application, I implement some protection for 'Login CSRF' attacks, a variant of CSRF attacks, by setting a cookie containing a random token on the login screen before the user logs in, and checking that token when the user submits their login details. Read more about Login CSRF from Google. A side effect of this is that the moment they do log in, I can check for the existence of that cookie - an extra redirect is not necessary.

blocks|key|353423|text|如果只想检查是否启用了会话AspxAutoDetectCookieSupport.+(在会话生存期内存在的cookie+)，请在web.config文件中将会话模式设置为AutoDetect+cookie，然后Asp.Net框架将向客户端浏览器写入一个名为cookie的cookie然后，您可以在Request.Cookies集合中查找此cookie，以检查客户端上是否启用了会话cookie。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|353424|例如，在您的web.config文件集中：|353425|<sessionState+cookieless="AutoDetect"+/>|code-block|syntax|javascript|353426|然后使用以下命令检查客户端上是否启用了cookies：|353427|if+(Request.Cookies["AspxAutoDetectCookieSupport"]+!=+null)++{+...+}|353428|Sidenote:默认情况下设置为UseDeviceProfile，只要客户端支持，它就会尝试将cookie写入客户端，即使cookie被禁用。我觉得有点奇怪，这是默认选项，因为它看起来毫无意义-在客户端浏览器中禁用cookies并将其设置为UseDeviceProfile时，会话将无法工作，如果您支持不支持cookies的客户端的无cookies模式，那么为什么不使用AutoDetect并支持禁用cookies的客户端的无cookies模式……|353429|entityMap^0|D|R|2D|34|0|0|L|0|0|0|R|0|0|0|69|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|12|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@]|E|$]]|$1|O|3|P|5|J|7|16|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|T|$]]

If you only want to check if session cookies (cookies that exist for the lifetime of the session) are enabled, set your session mode to AutoDetect in your web.config file, then the Asp.Net framework will write a cookie to the client browser called AspxAutoDetectCookieSupport. You can then look for this cookie in the Request.Cookies collection to check if session cookies are enabled on the client. 

E.g. in your web.config file set:

<pre><code>&lt;sessionState cookieless="AutoDetect" /&gt;
</code></pre>

Then check if cookies are enabled on the client with:

<pre><code>if (Request.Cookies["AspxAutoDetectCookieSupport"] != null) { ... }
</code></pre>

Sidenote: By default this is set to UseDeviceProfile, which will attempt to write cookies to the client so long as the client supports them, even if cookies are disabled. I find it slightly odd that this is the default option as it seems sort of pointless - sessions won't work with cookies disabled in the client browser with it set to UseDeviceProfile, and if you support cookieless mode for clients that don't support cookies, then why not use AutoDetect and support cookieless mode for clients that have them disabled...

blocks|key|349730|text|我总是这样用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|349731|navigator.cookieEnabled|code-block|syntax|javascript|349732|根据w3schools的说法，“所有主流浏览器都支持cookieEnabled属性。”|offset|length|349733|但是，当我使用表单时，这对我是有效的，我可以指示浏览器发送额外的信息。|349734|entityMap|0|LINK|mutability|MUTABLE|url|http://www.w3schools.com/jsref/prop_nav_cookieenabled.asp^0|0|0|2|9|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@$I|X|J|Y|1|Z]]|A|$]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

I always used this:

<pre><code>navigator.cookieEnabled
</code></pre>

According to <a href="http://www.w3schools.com/jsref/prop_nav_cookieenabled.asp" rel="nofollow noreferrer">w3schools</a> "The cookieEnabled property is supported in all major browsers.".

However, this works for me when i am using forms, where i can instruct the browser to send the additional information.

blocks|key|3129356|text|通常，您可能只需要在用户在站点上执行某些操作后才检查cookie支持，例如提交登录表单、向购物车中添加商品等。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3129357|对我来说，目前，检查cookie支持与CSRF+(跨站点请求伪造)预防密切相关。|3129358|你可能应该去其他地方阅读more+about+CSRF，但它背后的想法是，其他网站可能会欺骗你的用户，让他们向你自己的网站提交他们选择的隐藏表单。解决方法是在查看者看到表单时设置cookie，并将匹配的令牌设置为隐藏的表单元素，然后在处理表单时，检查cookie和隐藏的表单元素是否都已设置且彼此匹配。如果是企图的CSRF攻击，站点将无法提供隐藏字段来匹配用户的cookie，因为在同源策略下，用户的cookie对用户是不可读的。|offset|length|3129359|如果提交的表单没有cookie，但它确实包含一个看起来有效的令牌，则可以由此得出结论，用户禁用了cookie，并抛出一条消息，指示用户应该启用cookie并重试。当然，另一种可能性是用户是企图的CSRF攻击的受害者。因此，当cookie不匹配时阻止用户也有防止攻击的副作用。|3129360|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Cross-site_request_forgery^0|0|0|C|F|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$F|U|G|V|1|W]]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

Usually, you might only need to check for cookie support after the user has taken some action on the site, such as submitting a login form, adding an item to their cart, and so on.

For me currently, checking for cookie support goes hand-in-hand with CSRF (Cross-Site Request Forgery) prevention.

You should probably go elsewhere to read <a href="https://en.wikipedia.org/wiki/Cross-site_request_forgery" rel="noreferrer">more about CSRF</a>, but the idea behind it is that other sites may trick or your users into submitting a hidden form of their choosing to your own site. The way around this is to set a cookie when the viewer sees a form, and set a matching token as a hidden form element, and then when processing the form, check that both the cookie and hidden form element were set and match each other. If it is an attempted CSRF attack, the site won't be able to provide the hidden field to match the user's cookie, because the user's cookie won't be readable to them under the same-origin policy.

If a form is submitted having no cookie, but it does contain a valid-looking token, then you can conclude from this that the user has cookies disabled and throw up a message indicating that the user should enable cookies and re-try. The other possibility, of course, is that the user is the victim of an attempted CSRF attack. So blocking the user when the cookie doesn't match will also have the side-effect of preventing that attack.

blocks|key|3129400|text|我使用了“balexandre”上面答案的一个更简单的版本。它试图设置并读取会话cookie，唯一的目的是确定cookie是否被启用。是的，这需要JavaScript也被启用。所以如果你想要一个标签，你可能会想要一个标签。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3129401|<script>
//+Cookie+detection
document.cookie+=+"testing=cookies_enabled;+path=/";
if(document.cookie.indexOf("testing=cookies_enabled")+<+0)
{
++++//+however+you+want+to+handle+if+cookies+are+disabled
++++alert("Cookies+disabled");
}
</script>
<noscript>
++++
++++<h1>This+site+requires+JavaScript.</h1>
</noscript>|code-block|syntax|javascript|3129402|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I'm using a much more simplified version of "balexandre"'s answer above. It tries to set, and read a session cookie for the sole purpose of determining if cookies are enabled. And yes, this requires that JavaScript is enabled as well. So you may want a tag in there if you care to have one. 

<pre><code>&lt;script&gt;
// Cookie detection
document.cookie = "testing=cookies_enabled; path=/";
if(document.cookie.indexOf("testing=cookies_enabled") &lt; 0)
{
 // however you want to handle if cookies are disabled
 alert("Cookies disabled");
}
&lt;/script&gt;
&lt;noscript&gt;
 &lt;!-- However you like handling your no JavaScript message --&gt;
 &lt;h1&gt;This site requires JavaScript.&lt;/h1&gt;
&lt;/noscript&gt;
</code></pre>

blocks|key|3342387|text|对于启用的cookie使用navigator.CookieEnabled+(它将返回true或false)和Html标记noscript。顺便说一句，navigator.cookieEnabled是javascript，所以不要把它键入为HTML|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3342388|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Use navigator.CookieEnabled for cookies enabled(it will return true of false) and the Html tag noscript. By the way navigator.cookieEnabled is javascript so don't type it in as HTML

blocks|key|349772|text|检查这段代码，它会对你有帮助.|type|unstyled|depth|inlineStyleRanges|entityRanges|data|349773|<?php
session_start();

function+visitor_is_enable_cookie()+{
++++$cn+=+'cookie_is_enabled';
++++if+(isset($_COOKIE[$cn]))
++++++++return+true;
++++elseif+(isset($_SESSION[$cn])+&&+$_SESSION[$cn]+===+false)
++++++++return+false;

++++//+saving+cookie+...+and+after+it+we+have+to+redirect+to+get+this
++++setcookie($cn,+'1');
++++//+redirect+to+get+the+cookie
++++if(!isset($_GET['nocookie']))
++++++++header("location:+".$_SERVER['REQUEST_URI'].'?nocookie')+;

++++//+cookie+isn't+availble
++++$_SESSION[$cn]+=+false;
++++return+false;
}

var_dump(visitor_is_enable_cookie());|code-block|syntax|javascript|349774|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

check this code , it' will help you .

<pre><code>&lt;?php
session_start();

function visitor_is_enable_cookie() {
 $cn = 'cookie_is_enabled';
 if (isset($_COOKIE[$cn]))
 return true;
 elseif (isset($_SESSION[$cn]) &amp;&amp; $_SESSION[$cn] === false)
 return false;

 // saving cookie ... and after it we have to redirect to get this
 setcookie($cn, '1');
 // redirect to get the cookie
 if(!isset($_GET['nocookie']))
 header("location: ".$_SERVER['REQUEST_URI'].'?nocookie') ;

 // cookie isn't availble
 $_SESSION[$cn] = false;
 return false;
}

var_dump(visitor_is_enable_cookie());
</code></pre>

blocks|key|3129446|text|<?php+++session_start();
if(SID!=null){
++echo+"Please+enable+cookie";
}
?>|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|3129447|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>&lt;?php session_start();
if(SID!=null){
 echo "Please enable cookie";
}
?&gt;
</code></pre>

blocks|key|349798|text|cookieEnabled属性返回一个布尔值，用于指定是否在浏览器中启用cookies|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|349799|<script>
if+(navigator.cookieEnabled)+{
++++//+Cookies+are+enabled
}
else+{
++++//+Cookies+are+disabled
}
</script>|code-block|syntax|javascript|349800|entityMap^0|0|D|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

The <code>cookieEnabled</code> property returns a Boolean value that specifies whether or not cookies are enabled in the browser

<pre><code>&lt;script&gt;
if (navigator.cookieEnabled) {
 // Cookies are enabled
}
else {
 // Cookies are disabled
}
&lt;/script&gt;
</code></pre>

blocks|key|349808|text|NodeJS+-服务器端-+Cookie检查重定向中间件-快速会话/Cookie解析器|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|349809|依赖项|349810|var+express+=+require('express'),
++++cookieParser+=+require('cookie-parser'),
++++expressSession+=+require('express-session')|code-block|syntax|javascript|349811|中间件|349812|return+(req,+res,+next)+=>+{
++if(req.query.cookie+&&+req.cookies.cookies_enabled)
++++return+res.redirect('https://yourdomain.io'+%2B+req.path)
++if(typeof(req.cookies.cookies_enabled)+===+'undefined'+&&+typeof(req.query.cookie)+===+'undefined')+{
++++return+res.cookie('cookies_enabled',+true,+{
++++++path:+'/',
++++++domain:+'.yourdomain.io',
++++++maxAge:+900000,+
++++++httpOnly:+true,
++++++secure:+process.env.NODE_ENV+?+true+:+false
++++}).redirect(req.url+%2B+'?cookie=1')
++}
++if(typeof(req.cookies.cookies_enabled)+===+'undefined')+{
++++var+target_page+=+'https://yourdomain.io'+%2B+(req.url+?+req.url+:+'')
++++res.send('You+must+enable+cookies+to+view+this+site. Once+enabled,+click+<a+href="'+%2B+target_page+%2B+'">here</a>.')
++++res.end()
++++return
++}
++next()
}|349813|entityMap^0|0|C|0|0|3|0|0|0|3|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|V|8|@$9|W|A|X|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|O|3|P|5|J|7|12|8|@]|D|@]|E|$K|L]]|$1|Q|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|R|$]]

NodeJS - Server Side - Cookie Check Redirect
Middleware - Express Session/Cookie Parser 

Dependencies

<pre><code>var express = require('express'),
 cookieParser = require('cookie-parser'),
 expressSession = require('express-session')
</code></pre>

Middleware

<pre><code>return (req, res, next) =&gt; {
 if(req.query.cookie &amp;&amp; req.cookies.cookies_enabled)
 return res.redirect('https://yourdomain.io' + req.path)
 if(typeof(req.cookies.cookies_enabled) === 'undefined' &amp;&amp; typeof(req.query.cookie) === 'undefined') {
 return res.cookie('cookies_enabled', true, {
 path: '/',
 domain: '.yourdomain.io',
 maxAge: 900000, 
 httpOnly: true,
 secure: process.env.NODE_ENV ? true : false
 }).redirect(req.url + '?cookie=1')
 }
 if(typeof(req.cookies.cookies_enabled) === 'undefined') {
 var target_page = 'https://yourdomain.io' + (req.url ? req.url : '')
 res.send('You must enable cookies to view this site.&lt;br/&gt;Once enabled, click &lt;a href="' + target_page + '"&gt;here&lt;/a&gt;.')
 res.end()
 return
 }
 next()
}
</code></pre>

How can I detect on the server (server-side) whether cookies in the browser are disabled? Is it possible?

Detailed explanation: I am processing an HTTP request on the server. I want to set a cookie via the <code>Set-Cookie</code> header. I need to know at that time whether the cookie will be set by the client browser or my request to set the cookie will be ignored.

How to detect server-side whether cookies are disabled

中间件

服务器

如何在服务器端(服务器端)检测浏览器中的cookie是否被禁用？有可能吗？详细说明：我正在服务器上处理一个请求。我想通过Set-Cookie头设置一个cookie。我需要知道此时cookie是由客户端浏览器设置的，还是我设置cookie的请求将被忽略。

问如何检测服务器端是否关闭了cookie
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何检测服务器端是否关闭了cookieEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何检测服务器端是否关闭了cookie
EN