I just noticed this yesterday. My processing sketches on willhay.io have stopped working in Google Chrome and Firefox, however, they work fine in Safari. I haven't changed their code so it is very strange. Console is giving me this error
GET http://willhay.io/cdn-cgi/pe/bag2? r[]=http%3A%2F%2Fwillhay.io%2Fprocessing%2Fprocessing.min.js 405 (Not Allowed)
Something to do with Cloudflare maybe (I've just got the free version)? Check it out for yourself here:
http://willhay.io/processing/trip/
Turns out it was CloudFlare and the way their RocketLoader page speed optimizer works. I just turned it off after remembering I switched it on the other day and the Processing sketches are now working fine. Had something to do with the way it messes with the javascript and I guess processing.js didn't like that.
Related
We are seeing a really weird issue with our production site where after 30 seconds it appears that the session is invalidated in the Chrome and Edge browsers. We don't see any errors in the chrome inspect console.
We saw this behavior on 25MAY2022 right around when chrome 102 got pushed to the browsers at 5pm. IF we use inspect and turn off the cache then we don't see any issues with loading the site and everything operates fine.
FireFox works fine.
I'm using chrome 101.0.4951.61 against the same site on my android 11 phone and I cannot reproduce the issue.
Are there any new features in 102 we could turn off to see if a specific new security check might be at play?
My team is experiencing a similar issue when calling our API. If you go to chrome://flags/#private-network-access-send-preflights, and disable it, does that resolve your issue? If it does, then adding this header to your site may resolve the issue:
Access-Control-Request-Private-Network: true
We are currently doing pre-prod testing which is so far promising.
https://developer.chrome.com/blog/private-network-access-preflight/
Chrome ERROR_TIMED_OUT in latest version
yesterday morning I was happily working on my xsltforms in a hosted exist-db environment and at lunchtime, my chrome version updated. Since then, the forms load only white screens. Asking my colleagues, it turns out that these forms stopped being viewable in Edge and Firefox as well, sometime in the last few weeks. My laptop (not updated) still views the forms fine (or did until this morning when it's version of chrome also updated).
There is no error in the console (post edited for this) and the sources correctly list both the xml and the xsl fie. But the screen stays completely blank...
Nothing has changed in the config (and like I say the forms were working in the older version of chrome).
Any ideas on how to get them back?
Cheers
Ralph
Solved this problem by upgrading the XSLTforms main files from v.661 to v.662 (https://github.com/AlainCouthures/declarative4all/tree/master/public/direct). Not at all sure why this made such a dramatic difference, or why the fault suddenly kicked in on browser upgrade, but at least it's fixed.
So upon near completion of my website i tested it (as i do) in Chrome, FF, Opera and IE8. Ive not got around to Safari yet, but im guessing its mostly similar to how Chrome would display it.
A page that was working fine previously (about a week ago) has now, along with 2 other pages, stopped showing altogether in IE8. Cant seem to find any problem in the source. I have Firebug and no errors show up there either.
Ive also uploaded it to w3c.org's Validator and no major problems are found.. (majority are unescaped & in urls)
the doctype is XHTML 1.0 Transitional. Any one know of any reason IE8 sucks so bad and is halting my progress?
I forgot to mention my page loads content via AJAX calls. Could this maybe have something to do with it?
You could try to use a tool like Charles to record and peruse server interaction. Then at least you can see if the calls are returning expected headers.
I'm posting this question here, but I'm not 100% sure where the problem lies. I have a site hosted through Media Temple that I'm developing. It's started to continually give me http 206 responses (partial content) on image and js assets. I see these through firebug. This results in missing images and js files, or in some browsers like Safari, half rendered images. When I view my work off my local server I see no issues.
I see this behavior on all browsers, firefox 3.6, safari 5.0.3, chrome 8. I work off of mac os x 10.6.6. Different images exhibit this behavior at different times, and the only thing that works temporarily is to clear the cache, but I'll typically begin to see the problem again shortly.
The other thing, as much as I can tell, I don't see this problem on other machines. My work machine (also a Mac) doesn't show this behavior at all. The clients this site is for have never complained of these issues at all.
I've also taken some of these problematic assets and moved them to other servers and pointed my browser there, no problem, so it doesn't seem to be a corrupt file.
I've run out of places to look and was hoping someone on these forums might have some suggestions. This is a real mystery and would love to get to the bottom of it.
Sounds like a problem on the server side. Have you tried restarting the web server or taking a look at the error log?
I'm currently finishing up testing a new Ruby on Rails app. Just recently, some of the pages do not seem to finish downloading in IE8. In FireFox, Chrome and Safari, everything works perfectly. The pages all validate successfully using the W3C validator.
When I view the page source in IE8, the page has been chopped off around 75% of the size it should be. IE8 claims the page is finished loading, and doesn't give any errors, but of course the page isn't rendering properly.
Has anyone seen this before? I'd really appreciate any help.
Have you tried to watch the http requests, using something like Http Analyzer or HttpWatch (like firebug for IE)? That might shed some light if there is a problem with a JS or CSS file not being found, or if the server is returning something other than a 200.
HttpWatch has a free version at http://www.httpwatch.com/download
IE8 Comes with a built in developer toolbar. Just press F12.
You should be able to diagnose most problems using it.
Also, open the page in Firefox with the Webdeveloper Toolbar addon and check if any javascript issues are arising. I find that sometimes you may only see the error in IE8 but you might only figure out what is wrong using Firefox. Give it a try!
There was a javascript call in the page that needed to be wrapped with:
document.observe("dom:loaded", function() { ... };
in order to work in IE. Apparently, it was disruptive enough to kill the entire page render. Thanks BenTheDesigner!
Since this is the first result on a Google search for IE8 not completing a page request, I thought I'd add on that I've seen the same symptoms caused by Sophos Anti Virus' Browser Helper Object which interferes with page requests and thus doesn't complete download requests every time.
Hitting F5 resolves the issue most of the time but a click to the next page can cause it to reappear. Other symptoms include odd page rendering of background images, incorrect repeating or no repeating being done at all despite a CSS declaration specifically telling a background to repeat. I spent a week debugging my CSS and XHTML only to eventually try disabling all the browser "Add-ons" and all of a sudden the issue went away.
I nailed it down to Sophos' BHO and now no rendering issues.