Home > Web Front-end > HTML Tutorial > Static web pages contain css. It is no problem to open the file directly, but after deployment to IIS, access is not normal_html/css_WEB-ITnose

Static web pages contain css. It is no problem to open the file directly, but after deployment to IIS, access is not normal_html/css_WEB-ITnose

WBOY
Release: 2016-06-24 12:01:36
Original
2012 people have browsed it

My static web page can be opened with 360 Secure Browser by double-clicking index.html. However, after it is deployed to IIS, it cannot be accessed with 360 Browser. There is no problem with IE11, nor can IE8. I guess it is a browser compatibility issue, but there is no problem with 360 Secure Browser (version 6.3.1.196) direct access (double-click index.html directly). Experts please help!


Reply to discussion (solution)

If this is deployed online, an online address will be provided. Without an online address, there is no way to help you debug.

Sorry. This is the boss's project and requires confidentiality. So it cannot be announced. Currently, after deployment, it can only be viewed using 360 compatibility mode and browsers after IE8. I just find it strange that there is no problem in opening web files directly using 360 for static pages, but there is a problem when placing them in IIS. Settings about static pages in IIS. I don't understand the reason. Very disturbing.

If there is no problem opening it locally, it depends on the server configuration.

Yeah, that makes sense! I just don’t know what the specific reason is. I'm not familiar with the configuration in IIS. I installed all CSS-related static web page options. But it still doesn’t work. Has anyone encountered this problem?

What does abnormal mean? Is the page cluttered or something? Is the link tag attribute that was imported into the css missing?

Please post the specific pictures.

The link tag is not lost. The specifics are this.
Use 360 ​​Secure Browser (both modes are the same) to access the website deployed to IIS, as shown in the figure

Use 360 ​​Secure Browser (compatibility mode) to directly open the web page to block pop-ups, as shown in the figure

This appears after allowing the blocking

After clicking OK
the display is normal

In addition, IE11 accesses IIS web pages normally. When opening the web page directly, a script or plug-in block will pop up. After allowing it, it is normal. Display

that is, open the web page file directly. IE11 (IE8 and later) and 360 can display it normally under the slightest conditions that allow scripts and plug-ins. However, after being deployed to IIS and accessed through url, 360 cannot.

It may be a security setting issue. . 360 has 2 modes, one is compatible and the other is webkit mode. .

It may be that it is in webkit mode by default after release, so there is no prompt to run the plug-in. You should also see layout errors when you use chrome to access your website. You should switch to compatibility mode (IE core) and take a look

There is a difference between opening a webpage directly and publishing it in a safe area. . After release, the security zone is the Internet and the local area is the intranet. The Internet has more restrictions than the intranet. . Check the configuration yourself

Reconfigure the activx permissions in the internet area to allow creation instead of prompts

Solution: 1. Go to IE options and turn off the prompt
2. Write code, Change the registry
Reference
http://www.cnblogs.com/fanyf/archive/2011/05/05/2037332.html

Sorry for the late reply. I saw it two days ago and tried it according to your answers, but it didn't solve the problem. Your answer is to solve the problem of pop-up blocking. Later I found out that there was still a compatibility issue. Use 360 ​​to open the file directly. The browser uses Ie 5.5 quirks mode, so the display is normal. After publishing using IIS, 360 Browser adopts IE 5.5 standard mode and displays abnormally.
So I added the statement , and added in the head section to force the browser to use the latest version of the standards mode. Then I modified the CSS code in the web page that did not comply with W3c standards. Now it can be accessed by IE and 360, two browsers with IE as the core. FireFox still has compatibility issues. I really don’t have time to change it and fix it later. Thank you for your answers. Although they did not directly solve the problem, they gave a lot of hints. Scored.

I paid 50 for each person. It was the first operation and it was quite right. Hahaha.

Related labels:
source:php.cn
Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn
Popular Tutorials
More>
Latest Downloads
More>
Web Effects
Website Source Code
Website Materials
Front End Template