Configuration Error

Domain Name "www.stutteringhelp.org/pressrm" Does Not Exist In The Database

rCommunity.info supports multiple portals from a single database/codebase. It accomplishes this by converting the URL of the client browser Request to a valid PortalID in the Portals database table. The following steps describe the process:

1. 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.

    • 2. Application_BeginRequest ( globals.asax.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: http://www.rCommunity.info/default.aspx = Domain Name: www.rCommunity.info
    URL: http://205.68.157.167/default.aspx = Domain Name: 205.68.157.167
    URL: http://rCommunity.info/directory/default.aspx = Domain Name: www.rCommunity.info/directory

  • Using the Domain Name, the application queries the database ( Portals table - PortalAlias field ) to locate a matching record.

    Note: If there are multiple URLs which correspond to the same portal then the PortalAlias field must contain each valid Domain Name in a comma seperated list.