I just upgraded my browser to Safari 4 and find that our website is having some major issues specific to that browser version. As I click through pages on our site it takes one or two clicks before the browser window simply goes blank. When the window goes blank, there is no source to view and no matter how many times I try to reload or if I try to load other pages of the site, I still get the blank window. It's as if the server takes the request and simply returns a blank page.
If I wait over 15 seconds and then hit refresh again, the page loads fine. Not sure why it starts working again... Maybe a cache issue???
It's a PHP site and I've tried turning on error_reporting(E_ALL);, but that doesn't give any information. I also tried putting an echo statement at the very beginning of the index.php file and verified that the page still goes blank without echoing that statement, so I'm thinking the problem is not php code specific. The Apache error log does not show any issues. I have the same site on my local development server and it doesn't have the problem.
Safari 4 is the only browser that shows this problem. Does anyone have any ideas how to debug/fix this?
My webserver is ubuntu Hardy running Apache 2 an Mysql 5.
We have an nginx load balancer in front of the apache server and I just figured out that Safari 4 requires the nginx keepalive_timeout setting to be 0. Took all day to figure that one out...
I've been having the same issue with Safari 4 on my site but found that when reloading pages that return blanks, the request never even makes it to the server. No entry shows up in Apache's logs.
The keepalive setting for your LB sounds like a direction I could sniff in. Not sure what leeway I will have though, being on shared hosting.
Mike
This looks to be a safari bug. We experience it too, and I have read other reports.
http://discussions.apple.com/thread.jspa?threadID=2064488&start=0&tstart=0
Related
I have a J2EE App and I've been running it for a couple of years...
recently there's chance that whatever page I want to visit, it may show up as just Plain HTML and may not be rendered...
No Logs are written about this behavior as if it's a normal thing...
usually I click to visit a page, the Browser shows some cue about sending the request to the server... I can check that everything works just fine back there... Now there's 2 ways I can see this error :
1. I wait and wait and wait... and the browser is still waiting for a response... If I lose patience and press F5, the page shows up as PlainText HTML.
2. I wait till the end and the Browser may or may not load the page... if it loads the page, it's only partial and some parts of the Javascript or HTML may not load at all.
Pressing F5 usually fixes the problem but after a while, this may happen again...
This used to happen with Tomcat 6.x every once in a while but became worse after using Tomcat 7.x .
at first I thought it's related to my App but then I noticed this pattern happening even in Tomcat's own Admin pages such as its Session Manager.
What can I do ? I'm using Tomcat 7.0.54. upgrading it to newer versions didn't help...
Thank you...
A client's website was working fine, until they had some problems with their web host. Temporarily, the Apache CentOS Test Page was visible. The host claim the problem is fixed - and it seems to be - for everyone but me...
I'm using Safari 7 on OS X Mavericks and every single time when I visit their site I still see the test page.
When anyone else uses their own computer with any browser, it works fine...
When I use Chrome on my Mac it works fine... So the problem is just with Safari.
I've tried clearing Safari's cache
I've tried clearing the DNS cache
I've tried a restart
But I've got no idea why I can't access it. I need to access the site to work on it - yes I can use Chrome, but Safari is my primary browser. Any ideas?
It turned out this was caused by an issue in a Regex within Apache's Mod_Security. The Regex falsely identified a string contained within a cookie as being an SQL injection (it wasn't - purely coincidental).
For months we have been struggling with a weird issue on 1 of our Wordpress Network installations. We have 4 installations on 1 VPS and only one of the four installations generates this error.
The problem is that pages on all sites that run on that Wordpress Network installation, randomly(?) seem to try and parse the page as being RSS content. See this screenshot:
Full image
This only happens once per session (if it does at all) and after refreshing the page, all is good. This makes it extremely hard to fix, because debugging is almost impossible.
Whenever the issue seems to appear, the (RSS) content that is being displayed, is that of a different page..
Could this be a Wordpress issue, or could this be an issue in the Apache config?
Some domains we are encountering this on:
http://www.skynetsg.co.za/
http://www.workplacestrategies.co.za/
http://www.beachbreaks.co.za/
I hope there is someone that could help me solve this issue!
Update:
I just had the issue on the page: http://www.skynetsg.co.za/peter-sserwanga/ that was newly created. I checked the apache logs and they show nothing strange, just a 200 OK header..
Below is a link that may fix your problem. If your running WHM/Cpanel, you may have to recompile apache with out certain modules.
rss-feed-displayed-instead-of-html-page
UPDATE: This bug appears to be Browser Specific to Chrome. I've clicked the link about 50 times each in Firefox and IE and I can't seem to cause it. Also, once it is occurring, I can switch to FF or IE and it'll work fine on those two.
I have a particular page in my Rails 3 application on heroku that loads fine for awhile. I can click the same page and it loads without a problem. But after a certain number of loads, it suddenly starts to give me a 400 Bad Request Error with nginx/0.7.67 below it.
After it occurs once, everytime I load the page I get the 400 error. But if I leave the application alone for awhile, overnight for example, the page works again in the morning for a short while. But if I click the page a few times, it begins giving me that error again.
It's not something that occurs locally so it seems like it must be a heroku issue.
I also tried restarting heroku but that doesn't help. The only thing that seems to help is giving it some time off.
The heroku logs don't give me any new info as far as errors. Everything appears to be working fine and then I get a line that ends 727 | https | 400 and it just stops.
I'm using https if that helps.
The full error heroku log is:
[33m2011-07-02T15:25:59+00:00 heroku[nginx]: <-[0m GET /matters/show/34 HTTP/1.1 | 10.212.125.194 | 727 | https | 400
Let me know what code from this page would help solve this problem if you have an idea.
So after a long back and forth with the Heroku Support staff we finally found the issue. I was using Datatables in various places around my site and using cookies to store user state settings. That cookie was getting longer and longer and longer as a user navigated around the site until my header surpassed the maximum header size allowed by NGINX (8K).
The solution was to remove/simplify that cookie or switch from nginx Heroku (bamboo) to a Heroku stack that didn't use nginx (cedar).
I have a dynamic site I have made on PHP/MySQL and recently I have experienced a weird issue - sometimes (about once in four times) when I reload the active page the safari web browser (on a mac) automatically downloads the xxxx.php page rather than reloading it! I am trying to figure out what could be causing this, but i have no idea. Any suggestions?
The Content-Disposition HTTP Header is the only thing I can figure. Is there any way you can post something that we can test?
could it be with the .htaccess? I had a similar problem last month and I had to change some entries in my .htaccess, the shared server may have changed Apache's settings and it sopped working properly.