• Documentation
  Kentico development modelsInstallationUsing the Kentico interfaceDeveloping websitesConfiguring KenticoManaging usersSecuring websitesDeploying websitesManaging website contentMultilingual websitesMacro expressionsExternal utilitiesIntegrating 3rd party systemsCustom developmentE-commerce featuresOn-line marketing featuresCommunity featuresRelease notes - Kentico 12
• Tutorial
  Getting started with KenticoUsing the Kentico interfaceSelecting your tutorial pathSite development overviewPortal Engine developmentMVC developmentMVC business tutorialResource hub for marketers
• API Examples
  Content managementOn-line marketingE-commerceSocial and CommunityDevelopmentConfiguration

1. Open your Kentico solution in Visual Studio.

2. Create a custom module class.

   • Add the class into a custom project within the Kentico solution.

     For basic execution of initialization code, you only need to register a "code-only" module through the API. You do NOT need to create a new module within the Modules application in the Kentico administration interface.

3. Override the module's OnInit method and assign a handler to the RequestEvents.Prepare.Execute event.

   C#

   Copy

   using System;
   using System.Web;
   using System.Collections.Specialized;
   
   using CMS;
   using CMS.DataEngine;
   using CMS.Base;
   using CMS.Helpers;
   
   // Registers the custom module into the system
   [assembly: RegisterModule(typeof(SSLRequestModule))]
   
   public class SSLRequestModule : Module
   {
       // Module class constructor, the system registers the module under the name "SSLRequests"
       public SSLRequestModule()
           : base("SSLRequests")
       {
       }
   
       // Contains initialization code that is executed when the application starts
       protected override void OnInit()
       {
           base.OnInit();
   
           // Assigns a handler called before each request is processed
           RequestEvents.Prepare.Execute += HandleSSLRequests;
   
           // Sets the URL port used for HTTPS requests
           URLHelper.SSLUrlPort = 443;
       }
   
       // Checks if requests are forwarded as SSL
       private static void HandleSSLRequests(object sender, EventArgs e)
       {
           if ((HttpContext.Current != null) && (HttpContext.Current.Request != null))
           {
               // Loads the request headers as a collection
               NameValueCollection headers = HttpContext.Current.Request.Headers;
   
               // Gets the value from the X-Forwarded-Ssl header
               string forwardedSSL = headers.Get("X-Forwarded-Ssl");
               RequestContext.IsSSL = false;
   
               // Checks if the original request used HTTPS
               if (String.Equals(forwardedSSL, "on", StringComparison.OrdinalIgnoreCase))
               {
                   RequestContext.IsSSL = true;
               }
           }
       }
   }

The example registers a custom module and overrides its OnInit() method (executed automatically when the application starts) to assign a handler that is called before each request is processed. The X-Forwarded-Ssl header is used to check if the original request was submitted via HTTPS before the SSL accelerator forwarded it to the application. If this is the case, the IsSSL property is set to true, so the system processes the request as if it used the HTTPS protocol. Also, the SSLUrlPort property is set to 443.