Domain Name Does Not Exist In The Database
This system supports multiple websites from a single database/codebase. It accomplishes this by converting the URL of the client browser request to a valid Portal row in the Portals database table. The following steps describe the process:
- Web Server Processing
- When a web server receives a request from a client browser, it compares the file name extension on the target URL resource to its Application Extension Mappings defined in IIS.
- Based on the corresponding match, IIS then sends the request to the defined Executable Path (aspnet_asapi.dll in the case of ASP.NET requests).
- The aspnet_isapi.dll engine processes the request in an ordered series of events beginning with Application_BeginRequest.
- HttpModule.URLRewrite OnBeginRequest (UrlRewriteModule.vb)
- The request URL is parsed based on the "/" character
- A domain name is constructed using each of the relevant parsed URL segments.
Examples:
URL: https://www.domain.com/default.aspx = Domain Name: www.domain.com
URL: https://209.75.24.131/default.aspx = Domain Name: 209.75.24.131
URL: https://localhost/DotNetNuke/default.aspx = Domain Name: localhost/DotNetNuke
URL: https://www.domain.com/virtualdirectory/default.aspx = Domain Name: www.domain.com/virtualdirectory
URL: https://www.domain.com/directory/default.aspx = Domain Name: www.domain.com/directory
- Using the domain name, the application queries the database ( PortalAlias table - column HTTTPAlias) to locate a matching record.
Note: If you are installing the application to a remote server you must modify the HTTPAlias field value in table PortalAlias for the record with proper PortalID, according to the rules defined above.