blocks|key|1772305|text|我想你说的“干净”是指300重定向。许多服务器和语言here的配置。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1772306|entityMap|0|LINK|mutability|MUTABLE|url|http://www.somacon.com/p145.php^0|Q|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I think by 'cleanly' you mean like with a 300 redirect. Config for a lot of servers &amp; languages <a href="http://www.somacon.com/p145.php" rel="nofollow noreferrer">here</a>.

blocks|key|1772397|text|我认为最干净的方式是所描述的here+on+IIS-aid.com。它只适用于web.config，所以如果你改变了服务器，你不必记住你使用403.4自定义错误页面或其他特殊权限所经历的所有步骤，它就能正常工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1772398|<configuration>
++<system.webServer>
++++<rewrite>
++++++<rules>
++++++++<rule+name="HTTP+to+HTTPS+redirect"+stopProcessing="true">
++++++++++<match+url="(.*)"+/>
++++++++++++<conditions>
++++++++++++++<add+input="{HTTPS}"+pattern="off"+ignoreCase="true"+/>
++++++++++++</conditions>
++++++++++++<action+type="Redirect"+redirectType="Permanent"+url="https://{HTTP_HOST}/{R:1}"+/>
++++++++</rule>
++++++</rules>
++++</rewrite>
++</system.webServer>
</configuration>|code-block|syntax|javascript|1772399|entityMap|0|LINK|mutability|MUTABLE|url|http://www.iis-aid.com/articles/how_to_guides/redirect_http_to_https_iis_7^0|E|J|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

I think the cleanest way is as described <a href="http://www.iis-aid.com/articles/how_to_guides/redirect_http_to_https_iis_7" rel="nofollow noreferrer">here on IIS-aid.com</a>. It's web.config only and so if you change server you don't have to remember all the steps you went through with the 403.4 custom error page or other special permissions, it just works.

<pre><code>&lt;configuration&gt;
 &lt;system.webServer&gt;
 &lt;rewrite&gt;
 &lt;rules&gt;
 &lt;rule name="HTTP to HTTPS redirect" stopProcessing="true"&gt;
 &lt;match url="(.*)" /&gt;
 &lt;conditions&gt;
 &lt;add input="{HTTPS}" pattern="off" ignoreCase="true" /&gt;
 &lt;/conditions&gt;
 &lt;action type="Redirect" redirectType="Permanent" url="https://{HTTP_HOST}/{R:1}" /&gt;
 &lt;/rule&gt;
 &lt;/rules&gt;
 &lt;/rewrite&gt;
 &lt;/system.webServer&gt;
&lt;/configuration&gt;
</code></pre>

blocks|key|1557218|text|Global.asax|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1557219|protected+void+Application_BeginRequest()
{
if+(!Context.Request.Url.AbsoluteUri.Contains("localhost")+&&+!Context.Request.IsSecureConnection)
Response.Redirect(Context.Request.Url.ToString().Replace("http:",+"https:"));
}|code-block|syntax|javascript|1557220|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Global.asax

<pre><code>protected void Application_BeginRequest()
{
if (!Context.Request.Url.AbsoluteUri.Contains("localhost") &amp;&amp; !Context.Request.IsSecureConnection)
Response.Redirect(Context.Request.Url.ToString().Replace("http:", "https:"));
}
</code></pre>

blocks|key|1772489|text|我使用经典的asp+(内部网)，在需要登录的页面上，logon+include文件执行重定向：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1772490|if+Request.ServerVariables("SERVER_PORT_SECURE")+<>+"1"+or+Request.ServerVariables("HTTPS")+<>+"on"+then+
++++Response.Redirect+"https://"+&+Request.ServerVariables("SERVER_NAME")+&+Request.ServerVariables("URL")
end+if|code-block|syntax|javascript|1772491|这当然不包括GET或POST数据。因此，实际上它是一个干净的重定向到您的安全页面。|1772492|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I use classic asp (intranet) and on pages that requires login the logon include file does the redirect: 

<pre><code>if Request.ServerVariables("SERVER_PORT_SECURE") &lt;&gt; "1" or Request.ServerVariables("HTTPS") &lt;&gt; "on" then 
 Response.Redirect "https://" &amp; Request.ServerVariables("SERVER_NAME") &amp; Request.ServerVariables("URL")
end if
</code></pre>

This of course does not include GET or POST data. So in effect it's a clean redirect to your secured page.

Is there a clean way to redirect all attempts to going to an HTTP:// version of a site to its HTTPS:// equivalent?

IIS7: HTTP->HTTPS Cleanly

服务器

有没有一种干净利落的方法可以将所有访问HTTP://版本的站点的尝试重定向到它的HTTPS://等效项？

问IIS7: HTTP->HTTPS
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问IIS7: HTTP->HTTPSEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问IIS7: HTTP->HTTPS
EN