1240349 - Operation insecure error when trying to use IndexedDB with file protocol

Status: RESOLVED WORKSFORME

(Core :: Storage: IndexedDB, defect, P5)

Description

[antigonos]

Attachment: test.html

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:43.0) Gecko/20100101 Firefox/43.0
Build ID: 20160105164030

Steps to reproduce:

Open the attached test file as file:///c:/1/test.html



Actual results:

The IndexedDB cannot be opened, a SecurityError is thrown: The operation is insecure.


Expected results:

The IndexedDB feature should be usable through the file protocol too.
It worked in 42 and before.
It also works in Chrome.

Comment 1

[antigonos]

After some investigation, the network.cookie.cookieBehavior=2 pref seems to cause the problem.

With the default '0' value the test file does work (but then of course all cookies are enabled by default).

Using the value '2', in the Cookies Exception box the site should be enabled individually
(interestingly, this box does not allow multiple entries with a 'file:///' protocol, the various URLs seem to reuse one common entry).

So it seems that before 43 the cookieBehavior pref was not considered for the 'file:///' protocols?

A bit confusing the situation, but at least there is no need now to go back to 42.

Comment 2

[YF (Yang)]

https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=b368fb1c13a5293dc492dca9fea2925c96182ae3&tochange=48700cf2b4af168110a66ecb1d7f19d0ea261b7d

bug 1147821.

Comment 3

[Jonathan Watt [:jwatt]]

Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)

Comment 4

[Kagami Rosylight [:saschanaz] (they/them)]

This works for me now.

Comment 5

[Andrew Sutherland [:asuth] (he/him)]

(In reply to antigonos from comment #1)

After some investigation, the network.cookie.cookieBehavior=2 pref seems to
cause the problem.

With the default '0' value the test file does work (but then of course all
cookies are enabled by default).

Using the value '2', in the Cookies Exception box the site should be enabled
individually
(interestingly, this box does not allow multiple entries with a 'file:///'
protocol, the various URLs seem to reuse one common entry).

So it seems that before 43 the cookieBehavior pref was not considered for
the 'file:///' protocols?

A bit confusing the situation, but at least there is no need now to go back
to 42.

COOKIE_BEHAVIOR 2 is reject; it is possible there was a transition to use the policy behavior. Permissions can be used to re-enable storage when the preference would be used.