blocks|key|1196656|text|您可以为所有控制器使用一个基类，并使用require属性对其进行修饰。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1196657|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You could use a base class for all of your controllers, and decorate that with the require ssl attribute.

blocks|key|982182|text|您始终可以在global.asax中的应用程序级别添加检查|type|unstyled|depth|inlineStyleRanges|entityRanges|data|982183|protected+void+Application_BeginRequest(Object+sender,+EventArgs+e)
{
+++if+(!HttpContext.Current.Request.IsSecureConnection)
+++{
++++Response.Redirect("https://"+%2B+Request.ServerVariables["HTTP_HOST"]
+++++++++++++++++++++++++++++++++%2B+HttpContext.Current.Request.RawUrl);
+++}
}|code-block|syntax|javascript|982184|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|$]]

You could always add a check at the application level in your global.asax

<pre><code>protected void Application_BeginRequest(Object sender, EventArgs e)
{
 if (!HttpContext.Current.Request.IsSecureConnection)
 {
 Response.Redirect("https://" + Request.ServerVariables["HTTP_HOST"]
 + HttpContext.Current.Request.RawUrl);
 }
}
</code></pre>

blocks|key|982213|text|将RequireHttpsAttribute注册为全局筛选器。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|982214|在global.asax中：|982215|protected+void+Application_Start()
{
++++GlobalFilters.Filters.Add(new+RequireHttpsAttribute());

++++//...+other+stuff
}|code-block|syntax|javascript|982216|entityMap^0|1|L|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|S|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

Register the <code>RequireHttpsAttribute</code> as a global filter.

In global.asax:

<pre><code>protected void Application_Start()
{
 GlobalFilters.Filters.Add(new RequireHttpsAttribute());

 //... other stuff
}
</code></pre>

blocks|key|1196756|text|这不是使用RequireHttps，但我认为这是一个更好的解决方案，因为它在MVC+Lifecycle中更快地捕捉到了重定向。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1196757|public+class+RedirectModule+:+IHttpModule
{
++++private+HttpApplication+_context;

++++public+void+Init(HttpApplication+context)
++++{
++++++++_context+=+context;
++++++++_context.PostResolveRequestCache+%2B=+HttpRedirect;
++++}

++++public+void+HttpRedirect(Object+src,+EventArgs+args)
++++{
++++++++if+(_context.Request.Url.Scheme+==+Uri.UriSchemeHttp)
++++++++{
++++++++++++//Redirect+to+https
++++++++++++var+scheme+=+Uri.UriSchemeHttps+%2B+"://";
++++++++++++var+authority+=+_context.Request.Url.Authority;
++++++++++++var+url+=+_context.Request.RawUrl;

++++++++++++var+redirectTo+=+scheme+%2B+authority+%2B+url;
++++++++++++_context.Response.PermanentRedirect(redirectTo);
++++++++}
++++}

++++public+void+Dispose()+{+}
}|code-block|syntax|javascript|1196758|这个想法来自于这个article。|1196759|您可以在Web.config中或在Global.asax中注册模块。我将在web.cofig中向您演示。|1196760|<system.webServer>
++++<modules>
++++++++<add+name="ConfigModuleName"+type="Your.Namespace.RedirectModule"/>
++++</modules>
</system.webServer>|1196761|entityMap|0|LINK|mutability|MUTABLE|url|http://blog.thedigitalgroup.com/chetanv/wp-content/uploads/sites/23/2015/06/image_thumb.png|1|http://alexwolfthoughts.com/efficient-mvc-redirects-using-an-http-module/^0|5|C|12|D|0|0|0|9|7|1|0|4|A|H|B|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@$9|13|A|14|1|15]]|E|$]]|$1|F|3|G|5|H|7|16|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|17|8|@]|D|@$9|18|A|19|1|1A]]|E|$]]|$1|M|3|N|5|6|7|1B|8|@$9|1C|A|1D|B|C]|$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|O|3|P|5|H|7|1G|8|@]|D|@]|E|$I|J]]|$1|Q|3|-4|5|6|7|1H|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]|Y|$5|T|U|V|E|$W|Z]]]]

This isn't using <code>RequireHttps</code> but I think it's a better solution because it catches the redirect sooner in the <a href="http://blog.thedigitalgroup.com/chetanv/wp-content/uploads/sites/23/2015/06/image_thumb.png" rel="nofollow">MVC Lifecycle</a>.

<pre><code>public class RedirectModule : IHttpModule
{
 private HttpApplication _context;

 public void Init(HttpApplication context)
 {
 _context = context;
 _context.PostResolveRequestCache += HttpRedirect;
 }

 public void HttpRedirect(Object src, EventArgs args)
 {
 if (_context.Request.Url.Scheme == Uri.UriSchemeHttp)
 {
 //Redirect to https
 var scheme = Uri.UriSchemeHttps + "://";
 var authority = _context.Request.Url.Authority;
 var url = _context.Request.RawUrl;

 var redirectTo = scheme + authority + url;
 _context.Response.PermanentRedirect(redirectTo);
 }
 }

 public void Dispose() { }
}
</code></pre>

The idea came from this <a href="http://alexwolfthoughts.com/efficient-mvc-redirects-using-an-http-module/" rel="nofollow">article</a>.

You can register the module in your <code>Web.config</code> or inside the <code>Global.asax</code>. I'll show you in the web.cofig.

<pre><code>&lt;system.webServer&gt;
 &lt;modules&gt;
 &lt;add name="ConfigModuleName" type="Your.Namespace.RedirectModule"/&gt;
 &lt;/modules&gt;
&lt;/system.webServer&gt;
</code></pre>

blocks|key|982299|text|在Global.asax.cs中，使用"RegisterGlobalFilters“注册全局属性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|982300|public+static+void+RegisterGlobalFilters(GlobalFilterCollection+filters)
{
++++filters.Add(new+RequireHttpsAttribute());
++++//e.g.+filters.Add(new+HandleErrorAttribute());
++++//e.g.+filters.Add(new+System.Web.Mvc.AuthorizeAttribute());++++++++++++
}|code-block|syntax|javascript|982301|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|$]]

In Global.asax.cs, use "RegisterGlobalFilters" to register global attributes.

<pre><code>public static void RegisterGlobalFilters(GlobalFilterCollection filters)
{
 filters.Add(new RequireHttpsAttribute());
 //e.g. filters.Add(new HandleErrorAttribute());
 //e.g. filters.Add(new System.Web.Mvc.AuthorizeAttribute()); 
}
</code></pre>

blocks|key|982338|text|在您的FilterConfig.cs中应用以下内容：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|982339|public+static+void+RegisterGlobalFilters(GlobalFilterCollection+filters)
{
+++++//+only+if+Debug+is+not+enabled,+do+not+require+https+for+local+development
+++++if+(!HttpContext.Current.IsDebuggingEnabled)
++++++++++filters.Add(new+RequireHttpsAttribute());

+++++//...+any+other+filters
}|code-block|syntax|javascript|982340|这应该会迫使你的应用程序在每个页面上都使用https。|982341|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|$]]

In your FilterConfig.cs apply this:

<pre><code>public static void RegisterGlobalFilters(GlobalFilterCollection filters)
{
 // only if Debug is not enabled, do not require https for local development
 if (!HttpContext.Current.IsDebuggingEnabled)
 filters.Add(new RequireHttpsAttribute());

 //... any other filters
}
</code></pre>

That should force your app to use https on every page.

I have read the previous posts about using the RequireHttpsAttribute to secure individual controllers:

<a href="https://stackoverflow.com/questions/1639707/asp-net-mvc-requirehttps-in-production-only">ASP.NET MVC RequireHttps in Production Only</a>

but is there a way to apply this to the entire site? Due to my host (discountasp.net) I cannot use the "RequireSSL IIS" setting.

MVC RequireHttps entire site

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我已经阅读了之前关于使用RequireHttpsAttribute保护单个控制器的帖子：但是有没有一种方法可以应用到整个网站上呢？由于我的主机(discountasp.net)，我不能使用"RequireSSL IIS“设置。

问MVC RequireHttps整个站点
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问MVC RequireHttps整个站点EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问MVC RequireHttps整个站点
EN