CODEWITHSUNDEEP
javascripthtmlurlhistorypushstate
Atadj
Atadj

Reputation: 7180

SecurityError: The operation is insecure - window.history.pushState()

I'm getting this error in Firefox's Console: SecurityError: The operation is insecure and the guilty is HTML5 feature: window.history.pushState() when I try to load something with AJAX. It is supposed to load some data but Javascript stops executing on error.

I'm wondering why this may be happening. Is this some server misconfiguration? Any help would be appreciated.

UPDATE: Yes, it was a server error with domain name not matching: http://en.wikipedia.org/wiki/Same-origin_policy

Upvotes: 81

Views: 182020

Answers (11)

Alex78191
Alex78191

Reputation: 3056

You should disable blocking of cross sire cookies in security settings of browser.

Upvotes: 1

Mathieu Dhondt
Mathieu Dhondt

Reputation: 8914

I had the same problem and it was caused by setting <base href=> to a naked domain while my server always served the www domain. Adding the www to the url in base href solved the issue.

Upvotes: 1

Ayoub Laazazi
Ayoub Laazazi

Reputation: 858

I had this problem on ReactJS history push, turned out i was trying to open //link (with double slashes)

Upvotes: 5

Rahul Dahal
Rahul Dahal

Reputation: 182

I solved it by switching tohttp protocol from the file protocol.

  • you can use "live-server" extension in VS code,
  • or, on node, use live-server [dirPath]

Upvotes: 1

LOVENEET SINGH
LOVENEET SINGH

Reputation: 193

replace serviceWorker.unregister() to serviceWorker.register() in index.js file

Upvotes: 1

Dror
Dror

Reputation: 2410

When creating a PWA, a service worker used on an non https server also generates this error.

Upvotes: 2

oliverguenther
oliverguenther

Reputation: 1097

We experienced the SecurityError: The operation is insecure when a user disabled their cookies prior to visiting our site, any subsequent XHR requests trying to use the session would obviously fail and cause this error.

Upvotes: 17

hectorpyco
hectorpyco

Reputation: 21

I had the same problem when called another javascript file from a file without putting javascript "physical" address. I solved it by calling it same way from the html, example: "JS / archivo.js" instead of "archivo.js"

Upvotes: 2

T.Todua
T.Todua

Reputation: 56341

You should try not open the file with a folder-explorer method (i.e. file://), but open that file from http:// (i.e. http://yoursite.com/ from http://localhost/)

Upvotes: 5

Adam
Adam

Reputation: 6122

In my case I was missing 'www.' from the url I was pushing. It must be exact match, if you're working on www.test.com, you must push to www.test.com and not test.com

Upvotes: 5

Matt
Matt

Reputation: 41832

Make sure you are following the Same Origin Policy. This means same domain, same subdomain, same protocol (http vs https) and same port.

How does pushState protect against potential content forgeries?

EDIT: As @robertc aptly pointed out in his comment, some browsers actually implement slightly different security policies when the origin is file:///. Not to mention you can encounter problems when testing locally with file:/// when the page expects it is running from a different origin (and so your pushState assumes production origin scenarios, not localhost scenarios)

Upvotes: 52

Related Questions