22

Getting an error on Stack Overflow when running any snippet on chromium browsers (tested on chrome and edge) it is working on Firefox though.

(index):1  Refused to display 'https://stacksnippets.net/' in a frame because it set 'X-Frame-Options' to 'sameorigin'.


console.log("Checking if Stack Snippets are working");

20
  • It seems Cloudflare is blocking requests to stack snippets, there might be a bit more criteria than "chromium browsers" because on one of my devices (or network, since this device runs on a network separate from the others that I checked) I can't reproduce the issue with Chromium browsers. Commented Oct 3 at 5:23
  • 1
    The problem started for me yesterday. As an interim fix there should be a a more informative message than "refused to connect". Commented Oct 3 at 6:17
  • 2
    Interestingly, I do get quite different response headers for the stacksnippets request in Edge (left) and Firefox (right). Notably, in Edge I get the X-Frame-Options (which is what blocks the Stack Snippet from running), while I don't get that in Firefox. But the number of headers is also just different. Moreover, I do get some sort of specific header for Firefox (X-Firefox-Spdy ) on the request made from Firefox. Which leads me to suspect the server does have different responses for browsers. Commented Oct 3 at 6:27
  • 1
    This problem also started for me around 1-2 weeks on Chrome. On Firefox it seems to work normally Commented Oct 3 at 7:19
  • 1
    I can confirm. First time I see this. Win 11 Chrome 140.0.7339.208 Commented Oct 3 at 8:13
  • 1
    Can also confirm on 140.0.7339.185 arm64 MacOS 15.6. Guess we'll need to wait for the staff to wake up? Commented Oct 3 at 8:17
  • Ditto 141.0.7390.55 Commented Oct 3 at 10:25
  • 3
    Just FYI I opened a question at meta.stackoverflow.com/questions/435139/… with more details which is now marked as a duplicate of this one. I don't believe this has anything to do with X-Frame-Options the response code is 403 which is means the request is unauthenticated and that 403 response is not embeddable but the root cause is the 403 rather than the X-Frame-Options. I think this has something to do with the latest Chromium experimental features with partitioned 3rd party cookies. Commented Oct 3 at 10:43
  • I think not, unless they added that to the chrome browser without telling me or updating the browser. I had mo problem yesterday and today I have Commented Oct 3 at 11:14
  • 1
    Same with IMAGES in a post https://i.sstatic.net/IxTwi7DW.png Request Method GET Status Code 403 Forbidden Referrer Policy strict-origin-when-cross-origin Commented Oct 3 at 11:21
  • 1
    I'm having issues with images -- "i.sstatic.net/fzeGaNb6l.png net::ERR_BLOCKED_BY_RESPONSE.NotSameOrigin 403 (Forbidden)". I was able to open the link in a new tab and that presented a Cloudflare reCAPTCHA. Once I proved I was not a robot, the image showed in the new tab, but still does not show in the question/post. Chrome Version 141.0.7390.55 (Official Build) (64-bit) Commented Oct 3 at 16:16
  • 2
    Images issue just reported on MSE as well: Problem with images loading on Stack Exchange pages Commented Oct 3 at 17:47
  • @mplungjan it is my understanding that the experimental 3rd party cookie deprecation had been in the browser for over a year now but the rollout is gradual so it does not necessarily need to coincide with a new browser version or any sort of notice Commented Oct 4 at 7:47
  • Cannot reproduce on Windows 11 Pro, Google Chrome Version 141.0.7390.55 (Official Build) (64-bit). Commented Oct 4 at 20:25
  • Problem is no longer happening for me -- both snippets and images are working again. Commented Oct 6 at 14:52

0

Reset to default

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.