Home > front end >  IIS set HTTP permanent after 301 HTTPS, pseudo static failure?
IIS set HTTP permanent after 301 HTTPS, pseudo static failure?

Time:12-13

I wrote in the IIS URL rewrite an inbound rules, let all the HTTP access page to HTTPS, but the emergence of a new problem,

Such as I have a dynamic web page: http://www.a.com/a.aspx? Id=1

I wrote with pseudo static rules, the pseudo static page: http://www.a.com/a-1.html

I in the IIS setting site every page HTTP access to HTTPS, this set up, the HTTP page will get the HTTPS, but with the rules of pseudo static page, will go to the dynamic page,

But direct access to the HTTPS pages and do not have what problem,

For example, I visit: http://www.a.com/a-1.html, he will jump to https://www.a.com/a.aspx? Id=1, not to jump to https://www.a.com/a-1.html, the turning process of the pseudo static page?

Some people encountered such a problem?

How to deal with to access the pseudo static page under the HTTPS?

CodePudding user response:

More than 2000 postings, no one encountered this problem?
  •  Tags:  
  • IIS
  • Related