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.
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.
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.
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
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)
@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
This site is intended for bugs, features, and discussion of Stack Overflow and the software that powers it. You must have an account on Stack Overflow to participate.
X-Firefox-Spdy) on the request made from Firefox. Which leads me to suspect the server does have different responses for browsers.X-Frame-Optionsthe 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 theX-Frame-Options. I think this has something to do with the latest Chromium experimental features with partitioned 3rd party cookies.https://i.sstatic.net/IxTwi7DW.png Request Method GET Status Code 403 Forbidden Referrer Policy strict-origin-when-cross-origin