PHPFixing
  • Privacy Policy
  • TOS
  • Ask Question
  • Contact Us
  • Home
  • PHP
  • Programming
  • SQL Injection
  • Web3.0

Friday, April 15, 2022

[FIXED] Why after --disable-web-security and deleting x-frame-options header this error still showing?

 April 15, 2022     code-injection, cross-domain, electron, google-chrome, iframe     No comments   

Issue

I'm creating a webapp in electron, a web-crawler with a neural network, which needs all webSecurities to be disabled

i tried modifying the headers (X-Frame-Origin,access-control-allow-origin etc..) , using flags like chrome --allow-file-access-from-files --disable-web-security --user-data-dir="" etc... nothing seems to remove the error above

The iframe is showing the ORIGIN restricted websites after i modified the xframe header, but when i try to access its document, the error above pops

i tried running it in chrome and firefox, and the same behaviour is encoutered

been googling for 4 hours now and i can't seem to find an appropriate answer. if you think this is a duplicated please include a link, it would help a lot

error in chrome devtool


Solution

i found the solution ,the disable site isolation trial should be toggled on :

app.commandLine.appendSwitch('disable-site-isolation-trials')



Answered By - aymen ayoo
Answer Checked By - David Marino (PHPFixing Volunteer)
  • Share This:  
  •  Facebook
  •  Twitter
  •  Stumble
  •  Digg
Newer Post Older Post Home

0 Comments:

Post a Comment

Note: Only a member of this blog may post a comment.

Total Pageviews

Featured Post

Why Learn PHP Programming

Why Learn PHP Programming A widely-used open source scripting language PHP is one of the most popular programming languages in the world. It...

Subscribe To

Posts
Atom
Posts
Comments
Atom
Comments

Copyright © PHPFixing