Please, I need help about a strange behaviour of our server.
The server (Microsoft Windows Server 2012, IIS 8.5, Plesk Onyx 17.8.11) hosts a lot of sites developed in different technologies (PHP, ASP.NET, HTML+JS).
These sites work well with Chrome and FireFox both on Windows and MacOS, but Safari on iOS 11 & 12 is unable to open the sites, so I get this error "safari can't open the page because the server where this page is located isn't responding".
Sometimes Safari open the site for a few minutes, then it don't work again.
I experience a similar in Microsoft Edge: it can't open the sites unless I run Fiddler, in this case it works well.
I'm getting crazy, because this behaviour seems to be unpredictable.
Thank you in advance.
There are many compatibility issues for safari (I can't speak for edge). If you inspect the CSS code of these particular sites that you are having trouble running, and with some research, you will likely be able to identify the lines of code that are causing the sites not to load on Safari.
Related
I have a development environment for WordPress based on Windows 2012 R2 with some theme in Microsoft Azure.
If I deploy it to production which is also Windows 2012 R2 but in a local data center, it looks perfect the same on IE 11 and Google Chrome.
But on the client which has IE 9, the production (local) site is displayed different then the remote Development one. Menu's are different displayed.
When I compare the source (and replace the URL with a similar name) there's no difference between the two. So why is IE 9 rendering the local production site different?
I even searched for cases like one of the images is maybe harded linked to the development site, but that is not the case.
So, the only difference I can think of is that the production site has some name like :
http://Intranet/
versus
http://devintranet.cloudapp.net/
Could that be a difference in security settings local versus internet (which I cannot see from client perspective). And strange thing is that the Internet version is corrent and the local intranet version is different.
I have really no clue where to search for answers.
I found the solution....
IE9 was automatically adding intranet sites tot compatibility mode. It's a setting : Menu Tools > Compatibility view settings. Removing the intranet from the list and uncheck the box which was the default setting.
Why does MS put Intranet sites automatically in compatibility mode?? It has cost me hours and frustration.
I have started developing in C# MVC4 after 8 years of PHP and plenty of VB and C#.
My current problem is this: the application serves the images very slowly, yet only some of them. 32x32px images are served instantly, as they should, yet a 439KB PNG image is downloaded in over 30s. It's not a bandwidth problem, I checked on Remote Desktop Connection to the VPS that serves the files and it was slow to load there too.
Also jquery.min (181.5KB bundle) is 12.14s (measured by firebug).
I have tested with both static and dynamic compression ON / OFF, no improvement.
I have also tested with
<modules runAllManagedModulesForAllRequests="false"></modules>
on and off, still no improvement. I've had this problem both on Windows 2008 SP1 and on Azure.
Problem appears on IE9, FF, Chrome and Opera.
Any help will be appreciated.
Thanks.
Thank you for your support, the problem was caused by the ISP, and thanksfully their support fixed it.
Hello Stackoverflow community.
Since the release of Windows 8 and thus, Internet Explorer 10, FCKEditor refuses to function with IE10. With the latest patches, Firefox 17 and Chrome work just fine with it.
I know FCKEditor is old, so I was thinking of moving to CKeditor but it seems, its implementation for classic asp webpages doesnt work with IE10 as well.
Any suggestions, on how to fix the problem, or any other editors (with the functionality of the above two editors) would be appreciated(classic asp only).
CKEditor should work with IE10.
Maybe there are some problems with it at the moment (I tested it briefly some time ago), but given that it's a supported version (opposed to the status of FCKeditor), if you file bugs reporting the problems they should be fixed eventually.
I'd be very interested to hear what professional developers think about this, particularly frontend developers.
How do you go about testing your designs in multiple browsers? Do you use virtual machines, each with a different version of Internet Explorer installed? What is your setup/workflow?
So, what's the most efficient and reliable way to test a design in several legacy web browsers?
Thank you.
I mostly use Spoon virtualization. They removed IE from the service aftyer Microsoft told them to however it's still a good service for testing other browsers/versions.
For IE I tend to use the Microsoft provided IE VMs.
If you need virtualization product then VirtualBox is pretty good and free.
I've also just discovered Browserling which does something similar to Spoon virtualization and has support for multiple IE versions.
Oracle's VirtualBox is free. I have the following VMs set-up:
Windows XP - IE6, Firefox 3
Windows XP - IE7, Firefox 4
Windows Vista - IE8
Really, I don't test older versions of Firefox, Chrome, or Safari. All three of those browsers are on quick update cycles now and the push their updates almost immediately. The chance that users are still using an older version of those is much less than those using Internet Explorer.
Even now, I don't really test in IE6 anymore (thank god), but I know this is different depending on the audience of your website.
Really, if you can get away with it, do your basic testing in IE 7, 8, 9 and the latest versions of Firefox, Chrome, and Safari. Don't go completely out of your way to fix layout issues in older IEs; If you can get the information you want from the site, then the site is functioning. If someone complains about the site not looking exactly right, recommend they upgrade or switch browsers. "I can't upgrade from IE6 because my company uses it" is not really a valid excuse anymore with Chrome and Firefox being as light weight as they are, unless their computer admins have things completely locked down.
IE Tester allows to see web from ie5 till ie9.
http://www.my-debugbar.com/wiki/IETester/HomePage
It depends how legacy you wonna go but there is also Adobe browser lab.
This problem is beginning to annoy.
After my machine (Vista Ultimate) has been up for a while, running my ASP.NET web site project for debugging in VS2008 results in Internet Explorer "hanging". It doesn't seem to get past the network access stage, you know when it says "Loading web site", or "Waiting for".
I've attached a screenshot of IE. Note the status bar. It stays like that forever. I have to restart it and cross my fingers for it to work the next time. Invariably, it doesn't.
This happened with IE7 and IE8.
I am using the ASP.NET Web Development Server/Cassini. I have tried restarting this each time which seemed ot have got it, but then not so any more.
I'm up to date on patches.
ie screenshot http://img40.imageshack.us/img40/5446/iehanging.png
So thankfully Microsoft have finally released Security Essentials.
This meant I could de-install AVG (Free and paid-for versions) from my machine.
Hey presto, it works!
I would check the following
1) that your not starting IE against the webserver againt the wrong port, if your using the development IIS then it changes ports at times. That combined with you setting up the browser to launch against a the old port could create this problem.
2) Stop the local IIS and restart it (Again make sure your pointing towards the correct port)
3) Make sure you dont have any hung IE in task manager ( this happens to me sometimes ). Basiclly you have a IE in task manager that uses less then 1mb of ram and does not show on the taskbar, if thats the case kill them.
This doesn't sound, strictly speaking, like a hang. Can that tab/other tabs be navigated to other sites? Is your machine configured to use a proxy?
Is the request actually sent? Using Fiddler2 from www.fiddler2.com with the URL http://ipv4.fiddler:56125/ will show you, and help determine where in IE the problem might be.
I just had a similar problem that took about a week to unravel. Using AVG 9 Business Edition.
I'm on a Windows 7 machine with Visual Studio 2010 SP1, debugging ASP.NET sites running in IIS, with the same "hang" behavior you're seeing. Disabling LinkScanner and Online Shield in AVG fixed the problem.