CommuniGate Pro HTTP Modules
Intro
Installation
SysAdmin 
HTTP
Logs 
Protection 
Security 
Scalability 
Listeners 
VirusScan 
Alerts 
SNMP 
Events 
Dialup 
CLI/API 
Objects
Transfer
Access
Directory
Data Files
Clusters
WebApp
WebMail
Miscellaneous
Licensing
HowTo
HelpMe
  • Access to the Server WebAdmin Interface Pages
  • Access to the Domain WebAdmin Interface Pages
  • Access to the WebUser Interface
  • Access to Personal Web Sites
  • Configuring the HTTP module
  • Routing

    • The CommuniGate Pro HTTP modules implements the Hypertext Transfer Protocol via TCP/IP networks.

    The CommuniGate Pro Server uses the HTTP Admin module:

    The CommuniGate Pro Server uses the HTTP User module:

    Access to the Server WebAdmin Interface Pages

    The Server Administrator can use any Web browser application to configure and to monitor the Server remotely, using the Web (HTML) forms.

    The authentication schemes supported with the HTTP protocol protect the WebAdmin pages from an unauthorized access. In order to access the WebAdmin pages, the user should provide the name and the password of a CommuniGatePro account with required Server Access Rights.

    By default, the HTTP Admin module accepts clear text TCP/IP WebAdmin connections on the port 8010 and secure (SSL/TLS) connections on the TCP port 9010.

    To access the WebAdmin pages, the Server administrator should use the following URLs:
    http://domain.com:8010

    https://domain.com:9010
    where domain.com is the name of the main server domain or its alias, or the IP address of the CommuniGate Pro Server.

    Access to the Domain WebAdmin Interface Pages

    If the CommuniGate Pro Server supports several Secondary Domains, the same port can be used by the Domain Administrators to access the Secondary Domains settings and account lists.

    A domain administrator should access the server using the following URL:

    http://sub.domain.com:8010
    https://sub.domain.com:9010
    where sub.domain.com is the name of the secondary domain to administer.

    The server will ask for a user (Account) name and a password, and if the specified Account has the Domain Administrator access right, the list of the Domain Accounts is displayed.

    Sometimes this URL cannot be used. For example, a secondary Domain may have no DNS A-records (only MX records). To access such a Domain, its Domain Administrator should use the following URL:

    http://domain.com:8010/Admin/sub.domain.com/
    where:
    domain.com is the name of the Main Server Domain or its alias, or the IP address of the CommuniGate Pro Server.

    sub.domain.com is the name of the Domain to access.

    Server configuration errors can cut you off the Server WebAdmin Interface, if all your Server IP addresses and DNS names are assigned to secondary Domains. To access the Server WebAdmin Interface, use the following URLs:

    http://sub.domain.com:8010/MainAdmin/
    https://sub.domain.com:9010/MainAdmin/
    where sub.domain.com is any name pointing to your Server computer or any of its IP addresses.

    Other Domains can specify your Domain as their Administrtor Domain. Your Domain WebAdmin Login page provides a list of those Domains, so you can open their WebAdmin Interfaces. Remember that you should login using your full Account name (yourAccountName@yourDomainName) when accessing other Domain WebAdmin pages.

    Access to WebUser Interface

    CommuniGatePro users can connect to the CommuniGate Pro Server with any Web browser (via the HTTP protocol) to manage their accounts, to browse their mailboxes, to read, copy, delete, forward, and redirect messages, to move messages between mailboxes, to compose and submit new messages, etc. This CommuniGate Pro component is called the WebUser Interface.

    Registered users and guests can also use this component to browse mailing list archives.

    By default, the HTTP User module accepts clear text TCP/IP connections on the TCP port 8100, and the secure connections - on the TCP port 9100. If your Server does not have to coexist with some other Web Server on the same computer, it's recommended to change these port numbers to 80 and 443 - the standard HTTP and HTTPS port numbers.
    In this case your users will not have to specify the port number in their browsers.

    Access to Personal Web Sites

    CommuniGatePro users can have their personal Web Sites. See the Web Site section for the details.

    The URL for the account@domain personal Web site is:
    http://domain:port/~account
    where port is the WebUser port (8100 by default).

    The list of files on that personal Web Site can be seen at:
    http://domain:port/~account/index.html

    Configuring the HTTP modules

    Use any Web Browser to connect to the Administration Port on your Server, and open the Access page in the Settings section.

    Serving HTTP Admin Clients
    Log:
    Channels: listener
    Serving HTTP User Clients
    Log:
    Channels: listener

    Log Level
    Use this setting to specify what kind of information the HTTP module should put in the Server Log. Usually you should use the Major or Problems (non-fatal errors) levels. But when you experience problems with the HTTP module, you may want to set the Log Level setting to Low-Level or All Info: in this case protocol-level or link-level details will be recorded in the System Log as well.
    The HTTP Admin module records in the System Log are marked with the HTTPA tag.
    The HTTP User module records in the System Log are marked with the HTTPU tag.

    Channels
    This setting is used to limit the number of simultaneous TCP/IP connections the HTTP module can accept. Most browsers open several connections to load an HTML page and all embedded pictures, so do not set this limit to less than 5, otherwise some browsers may fail to download embedded graphic objects.

    listener
    Follow this link to open the HTTP Admin Port or HTTP User Port listner settings. There you can specify the TCP port number(s) the service should use, the interfaces to use, and other options.

    If the CommuniGate Server computer runs some other Web Server application, you should specify a port number in the "secondary range" to avoid conflicts with that other Web Server application. Usually the "secondary" Web Servers use ports numbers in the 8000-8100 range. If you set the port number to 8010, you will be able to connect to your server by entering http://xxx.yyy.zzz:8010 in your Web browser, where xxx.yyy.zzz is the exact domain name (A-record) or the IP address of your server.

    Routing

    As any Access module, the HTTP modules use the Router to process all address. But unlike other modules, the HTTP module often deals not with the complete E-mail addresses, but with domain names only.

    When a request is received on the WebAdmin port, the HTTP module should use the domain name or the IP address specified in the URL to decide which Domain Administration pages to display.

    When a request is received on the WebUser port, the HTTP module should use the name specified in the URL to decide which Domain (its login page, mailing lists, personal Web Sites, etc.) to access.

    In order to support all types of CommuniGate Pro Routing features (Router Table, Domain Aliases, IP Address to Domain Mapping, etc.), the HTTP module composes a complete E-mail address LoginPage@domainname (where domainname is the domain name specified in the request URL), and processes this address with the Router. If the addresses is routed to the LOCAL module, and the routed username is still LoginPage, then the domain part of the resulting address is used to open the proper CommuniGate Pro domain (the main domain or a secondary one).

    If the address is routed to the LOCAL module, but the resulting username is not LoginPage, the Personal Web Site of the addressed Account is opened.

    CommuniGate® Pro Guide. Copyright © 1998-2002, Stalker Software, Inc.