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).
Related
I have a JSF application that uses Primefaces 7.0. Some of its pages use the p:media component to display the content of PDF files. When installed on a remote linux server, the application does not show the content of the PDF if used with Firefox 67.0. It works fine with Chrome and IE. And it works perfectly on my Windows 10 PC, even with Firefox. To make it even wierder, inspecting the element makes it visible in my laptop, but not in my desktop computer. Has anyone else a similar problem? Please advice.
EDIT 11/11/2019: Today I learned that the problem occurs when using https instead of http. Therefore, it doesn't really matter that the server is remote; what happens is that on our remote (and public) server we use https
I am testing(on localhost on Windows 7 64 Bit) the behaviour of my web application when cookies are blocked.
When testing on IE11, it seems you cannot block cookies, even when the IE11 settings show that I have blocked cookies.(I have also tried uninstalling & re-installing IE11, just in case something was broken, but cannot block cookies.)
I have researched and been to the following places but no answers;
Cookies disable doesn't work in Internet Explorer 11 using advance setting
Cookie disabled issue in IE
document.cookie is still accessible on IE11, even though cookies are disabled
https://superuser.com/questions/1000545/internet-explorer-11-cant-disable-localhost-cookies
Or may be I should just forget about Internet Explorer ?
(Thanking the coding community in advance)
I think you are facing the same issue with me. i searched a lot too.
What i figure out is that Cookies setting only impact on websites which contains real domain (ie: examples.com, abc.net,...)
you can change the localhost domain by editing a host file in (C:\Windows\System32\drivers\etc)
Include one line at the end of that text file like below:
127.0.0.1 testweb.net
Now, whenever you type testweb.net, it will return the page as same as the localhost does.
I am using browserstack to test some devices, like IE. However I need to set up local testing so I can test my site localhost:3000
I have logged in to browserstack in Chrome and installed the extension. I click on the extension IE11 link. It takes me to a IE11 on Windows 8 virtual machine.
I type localhost:3000 into IE but it doesn't seem to work.
Then I click the Settings cog and click resolve all URLs through my network.
Still it doesn't seem to work for me.
Looks like the setup was fine in Browserstack, I just forgot that in IE11 I need to use http://localhost:3000 as it doesn't automatically resolve the protocol http silly mistake :)
I'm using microsoft's CDN for pulling down the Ajax libraries. And I'm using SSL on some pages.
This URL resolves fine in Firefox and IE:
https://ajax.microsoft.com/ajax/4.0/MicrosoftAjax.js
However in google chrome (on my PC, today...) it seems to time out with a very odd response:
On other PCs it seems to work fine, however I know I'm not the only one experiencing the problem as we've had occasional complaints from some of our clients about certain pages timing out and failing, that seems to point to the same problem.
As per my comment, I experienced the same issue but with Firefox failing and Chrome and IE succeeding.
Restarting the browser and the computer had no affect. Clearing the browser cache did fix the issue. I can only assume there was some kind of corruption in the browser cache.
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