blocks|key|312394|text|您最有可能通过file://+URI方案在本地文件上使用它，该方案不能设置cookies。把它放在本地服务器上，这样就可以使用http://localhost了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|312395|entityMap^0|7|7|1R|G|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

You're most likely using this on a local file over the <code>file://</code> URI scheme, which cannot have cookies set. Put it on a local server so you can use <code>http://localhost</code>.

blocks|key|3261338|text|在本地开发HTML5时，我也遇到了这个问题。我遇到了图像和getImageData函数的问题。最后，我发现可以使用--allow-file-access-from-file命令开关启动chrome，这样就摆脱了这种保护安全性。唯一的问题是，它会降低浏览器的安全性，而且你不能让一个chrome实例启用标志，而另一个实例不启用标志。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3261339|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 also had this issue while developping on HTML5 in local.
I had issues with images and getImageData function.
Finally, I discovered one can launch chrome with the --allow-file-access-from-file command switch, that get rid of this protection security.
The only thing is that it makes your browser less safe, and you can't have one chrome instance with the flag on and another without the flag.

blocks|key|3261495|text|面对同样的情况，使用Javascript+webworkers。不幸的是，Chrome不允许访问存储在本地文件中的javascript+worker。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3261496|下面使用本地存储的一种解决方法是在--allow-file-access-from-files上运行Chrome+(最后是s+)，但只允许一个Chrome实例，这对我来说不太方便。出于这个原因，我使用Chrome+Canary，允许文件访问。|style|CODE|3261497|顺便说一下，在Firefox中没有这样的问题。|3261498|entityMap|0|LINK|mutability|MUTABLE|url|/questions/tagged/webworkers^0|L|A|0|0|H|U|1P|1|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@$A|W|B|X|F|G]|$A|Y|B|Z|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|10|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]]]

Faced with the same situation playing with Javascript <a href="/questions/tagged/webworkers" class="post-tag" title="show questions tagged &#39;webworkers&#39;" rel="tag">webworkers</a>. Unfortunately Chrome doesn't allow to access javascript workers stored in a local file. 

One kind of workaround below using a local storage is to running Chrome with <code>--allow-file-access-from-files</code> (with <code>s</code> at the end), but only one instance of Chrome is allowed, which is not too convenient for me. For this reason i'm using Chrome Canary, with file access allowed. 

BTW in Firefox there is no such an issue.

blocks|key|3047729|text|如果您尝试使用数据URI方案创建web+worker，则会弹出此错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3047730|var+w+=+new+Worker('data:text/javascript;charset=utf-8,onmessage%2520%253D%2520function()%2520%257B%2520postMessage(%2522pong%2522)%253B%2520%257D');+w.postMessage('ping');|code-block|syntax|javascript|3047731|根据标准是不允许的：http://www.whatwg.org/specs/web-apps/current-work/multipage/workers.html#dom-worker|offset|length|3047732|entityMap|0|LINK|mutability|MUTABLE|url|http://www.whatwg.org/specs/web-apps/current-work/multipage/workers.html#dom-worker^0|0|0|A|2B|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

This error pops up, if you try to create a web worker with data URI scheme.

<pre><code>var w = new Worker('data:text/javascript;charset=utf-8,onmessage%20%3D%20function()%20%7B%20postMessage(%22pong%22)%3B%20%7D'); w.postMessage('ping');
</code></pre>

It's not allowed according to the standard: <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/workers.html#dom-worker" rel="noreferrer">http://www.whatwg.org/specs/web-apps/current-work/multipage/workers.html#dom-worker</a>

blocks|key|3047912|text|我在使用历史API时遇到了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3047913|window.history.pushState(null,+null,+URL);|code-block|syntax|javascript|3047914|即使使用本地服务器(localhost)，您也希望将'http://‘’添加到您的URL中，以便您拥有类似以下内容：|3047915|http://localhost...|3047916|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I had this issue when using the history API. 

<pre><code>window.history.pushState(null, null, URL);
</code></pre>

Even with a local server (localhost), you want to add 'http://' to your URL so that you have something similar to: 

<pre><code>http://localhost...
</code></pre>

blocks|key|3261381|text|我对--allow-file-access-from-files的解决方案并不完全满意，因为我使用Chrome作为我的主要浏览器，而且对我打开的这个漏洞也不是很满意。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3261382|现在，我正在使用Canary+(+chrome测试版)进行开发。对于我真正的博客来说，仅仅是Chrome版本:两个浏览器不共享标志！|3261383|entityMap^0|2|U|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

I wasn't completely happy by the <code>--allow-file-access-from-files</code> solution, because I'm using Chrome as my primary browser, and wasn't really happy with this breach I was opening.

Now I'm using Canary ( the chrome beta version ) for my development with the flag on.
And the mere Chrome version for my real blogging : the two browser don't share the flag !

blocks|key|3261509|text|如果在获得权限之前使用新的(目前仅限webkit+)通知功能，也可能收到此错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3261510|第一次运行：|3261511|
<button+onclick="webkitNotifications.requestPermission();">Enable+Notifications</button>|code-block|syntax|javascript|3261512|稍后运行：|3261513|//+Display+Notification:
window.webkitNotifications.createNotification('image',+'Title',+'Body').show();|3261514|请求权限函数需要由用户引发的事件触发，否则不会显示。|3261515|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

One can also receive this error if using the new (so far webkit only) notification feature before getting permission.

First run:

<pre><code>&lt;!-- Get permission --&gt;
&lt;button onclick="webkitNotifications.requestPermission();"&gt;Enable Notifications&lt;/button&gt;
</code></pre>

Later run:

<pre><code>// Display Notification:
window.webkitNotifications.createNotification('image', 'Title', 'Body').show();
</code></pre>

The request permission functions needs to be triggered from an event caused by the user, otherwise it won't be displayed.

blocks|key|3261533|text|在移动safari中，当使用ASP.NET+MVC返回一个带有重载的FileResult时，我遇到了这个错误，它返回的文件名与原始文件名不同。所以,|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3261534|return+File(returnFilePath,+contentType,+fileName);|code-block|syntax|javascript|3261535|会在mobile+safari中给出错误，其中|3261536|return+File(returnFilePath,+contentType);|3261537|不会的。|3261538|我甚至不记得为什么我认为我所做的是一个好主意。我猜是想变得聪明些吧。|3261539|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I was been getting that error in mobile safari when using ASP.NET MVC to return a FileResult with the overload that returns a file with a different file name than the original. So,

<pre><code>return File(returnFilePath, contentType, fileName);
</code></pre>

would give the error in mobile safari, where as

<pre><code>return File(returnFilePath, contentType);
</code></pre>

would not.

I don't even remember why I thought what I was doing was a good idea. Trying to be clever I guess.

I get the following error in Chrome's developer tools window when I try to set a cookie using <a href="http://code.google.com/p/cookies/" rel="noreferrer">this</a> jQuery plugin:

<blockquote>
 Uncaught Error: SECURITY_ERR: DOM Exception 18
</blockquote>

What does this error mean and how can I fix it? I get the same error when I use <a href="http://plugins.jquery.com/project/Cookie" rel="noreferrer">this</a> jQuery plugin.

Uncaught Error: SECURITY_ERR: DOM Exception 18 when I try to set a cookie

当我尝试使用 jQuery插件设置cookie时，在Chrome的开发人员工具窗口中出现以下错误：未捕获错误: SECURITY_ERR: DOM异常18这个错误意味着什么，我如何修复它？当我使用 jQuery插件时，我得到了同样的错误。

问尝试设置cookie时未捕获错误: SECURITY_ERR: DOM异常18
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问尝试设置cookie时未捕获错误: SECURITY_ERR: DOM异常18EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问尝试设置cookie时未捕获错误: SECURITY_ERR: DOM异常18
EN