Currently I just deployed a website from Debian local server. The Website seems to run very nicely until I reach internet explorer. Here is the run down.
I type in the IP address of the server and I get the website with no error.--->
http://imgur.com/IPpM4YH
Now I will try to reach the website via HostName instead of the ip address. But the website will not display correctly.---> http://imgur.com/UVb3bAb
Now this issue only persists in IE. Google, firefox, safari... etc will not encounter this problem.
Other interesting issues:
on some computers using the servers IPadress or the host name will not display the website correctly.
Php code does not generate the the imgs for the gallery.
style sheets are recognized but not applied to the overall website
Attempt fixes
lowering security on IE, adding it to website list.
reloading files on server
rebooting all machines.
It looks as though your Internet Explorer is using Compatibility View when you view the page using a host name. It does this if it thinks the page is 'internal' (as in Intranet).
Internet Explorer never uses Compatibility View if you navigate by IP address, because it cannot tell, so it assumes the website is external.
To get your page to be always displayed in standards mode, look at the questions already answered about this: IE10 renders in IE7 mode. How to force Standards mode?
Related
I have been playing around with the PIA desktop client and all kinds of VPN settings today, so it's not out of question that something I did screwed something else up, but whatever happened, whenever I now go to pandora.com it automatically directs me to privateinternetaccess.com.
I have restarted chrome, my PC, re-installed chrome, removed the PIA desktop client, removed the tunnelbear desktop client and chrome extension I still had installed and disabled all my other chrome extensions.
Accessing pandora.com through Edge or Chrome's incognito mode works fine.
Visiting http://www.pandora.com/restricted (Which is where I should land when visiting pandora.com, since I'm in Germany and currently w/o a VPN) actually loads the expected page from Pandora. So it's not like the entire domain is bricked.
Kinda out of ideas over here.
The thing I hadn't tried was just resetting Chrome, since I kinda forgot I can disconnect my Google Account first to not lose all my settings.
So yeah disconnecting google account -> resetting chrome -> reinstalling chrome(cause why not) fixed the issue.
I have a Razor MVC application that contains a link to open a PDF stored on a file server. My code works when I run it in Visual Studio but is not working when I try it on production on the same computer. I click the link and nothing happens, I can see the path when I hover over it though. There are no errors or anything. I've tried all browsers but only really care about IE.
View
Image when I hover over the link
Any ideas why this is not working?
Filesystem URLs from remote pages (i.e. pages on other protocols like http:// or even other directories in the file system) are blocked by modern browsers for security reasons.
Here is a page describing the behaviour for Firefox (along with reasons why it exists).
Internet Explorer has joined the ranks of these modern browsers:
By default, Internet Explorer prevents navigation to Uniform Resource
Identifiers (URIs) using the "file:" protocol when the current URL
matches the following conditions:
The current URL is opened in the Internet zone or the Restricted Sites zone.
The current URL uses a protocol other than "file:".
This is a security measure designed to
prevent malicious sites from accessing system file objects.
This can be changed, but only on a per-client basis (see the MSDN article for details.)
I have been stumped before, but never quite like this. Please bear with me.
I have embedded an MP4 video into a web page using the HTML5 video tag as follows:
<video poster="/media/video/cick_away_poster.png" controls width="560" height="315">
<source src="http://www.lpcsc.k12.in.us/media/video/click_away.mp4" type="video/mp4" />
<p>Your browser does not support this video.</p>
</video>
The page is hosted in house, on our corporation website. I tried both relative and absolute links, then used the complete URL to the video for troubleshooting on different servers outside of our network. More on this later.
I didn't think there was an issue until a few people in our corporation informed me that they could not see the video in IE11 on their PC.
I had them try it in Chrome and it worked fine.
I double-checked it in both IE11 and Chrome on my PC and it works
fine
I tried it on a freshly cast, fully updated Windows 7 PC, and it did
not work and just shows "Your browser does not support this video."
I tried it in Chrome on the new PC, and it works fine.
I used just the bare code needed for the video. No change.
At this point, I am already scratching my head. Why would it work on some machines and not others, but ONLY in IE11? Some coworkers can see it, yet others cannot?
Moving on:
I created a page on our Intranet server (also IIS) and another server
(Apache) and tested it. Same results.
I created a page on a test server at my home and tested it from the
new PC located in my office. Voila! It worked! Wait...what?
I located other HTML5 videos on other external sites, and all of them
also played on the same machine using IE11.
I tried the original page once again, just for kicks, and nothing.
I changed my IP to the IP of the new machine and vice versa. Nothing
I compared IE settings, security settings, made sure Windows Firewall
was disabled on both machines, compared network settings...you name
it. Nothing.
Now I am ready to drink. It makes no sense...
Just because, I decided instead of accessing the site using the FQDN, I'd try via the server's IP address. Bingo....it works. Huh?
To review:
In Chrome using FQDN - Video appears on all machines
In IE11 using FQDN - Hit and miss...appears on some, not on others.
In IE11 using pages hosted externally - Video appears on all machines
In IE11 using IP address of internally hosted server - Video appears on all machines
It led me to consider a DNS issue, but why would it work in Chrome on all machines? It is specific to IE, but only on SOME machines. I even flushed DNS for kicks....nothing.
I pointed this out to our network admin, and he is equally as stumped. No errors, it just acts like the browser is not HTML5 compliant when using the FQDN on some machines.
Anyone?
Seems I have answered my own question:
We are a large corporation and we image all of our Windows machines. The coworker who creates most of our images added our domain to the Compatibility Mode list in IE. Makes total sense now that I think about the behavior that was occurring, I just never thought about the fact that some machines were imaged while others were not.
I try to set up website. Everything works well on PC or Mac, but when I try display my website on my iPhone or Android device there is a problem. Website is not displaying correctly and after few clicks it crashes. My investigation led me to DNS. So:
I have domain - mydomain.org.
Domain indicates to my public address on my router and specific port - my_public_ip:public_port/directory_with_website
On router I have set rule - forward requests from public_port to ip_inside_lan:80
As I wrote everything works perfectly on PC and Mac. I type mydomain.org into my browser and website is displayed correctly. But on my phone not.
But strange thing is that when I type into my mobile browser address my_public_ip:public_port/directory_with_website it works perfect.
Any ideas or suggestions?
Thank you for help
So I have an interesting quirk that isn't making a lot of sense right now.
I am trying to create drop down menus for a website using CSS.
When I open the index.html file locally, it looks fine in Firefox, and it is all messed up in IE.
When I FTP the file to a server, it looks fine in both Firefox and IE.
I would like to be able to see what it is supposed to look like in IE locally, before uploading it to the actual site.
What would cause IE to render incorrectly on the local file, but correctly on a server?
For some reason, IE9 (and possibly 10, I'm not sure) runs Intranet sites in Compatability Mode, and it defines all locally viewed HTML files as intranet pages. So, when you're accessing local files, you may very well be accessing them roughly as if you're viewing in IE7.
Turning this off has been covered here.