Chapter D: Configuration Directives
AdminCGIPath
The AdminCGIPath configuration directive is the administrative analog to the CGIPath directive and allows for a distinct URL path to be used for access to the administrative interface and scripts (e.g. mt.cgi).
Its use is optional since the CGIPath setting is used in its absence. However, for added security, Six Apart recommends use of this directive in combination with SSL (via https) in order to provide encryption/authentication of all administrative requests.
The value of this setting can be included in a template via the MTAdminCGIPath template tag.
Examples
In your mt-config.cgi, the following (without AdminCGIPath) would be used for all links to Movable Type scripts, public or private:
CGIPath http://www.example.com/path/to/mt/
The following, in addition to the CGIPath setting above, would preferentially use the admin subdomain of example.com for accessing the administrative scripts. All public scripts would still use the CGIPath setting.
AdminCGIPath http://admin.example.com/path/to/mt/
The following, in addition to the CGIPath setting above, would use HTTP protocol for the public interface scripts and HTTPS for the administrative scripts. You would, of course, need to enable SSL on your server before this will work.
AdminCGIPath https://www.example.com/path/to/mt/
In this case, you will also need to set your StaticWebPath to a relative value in order to avoid insecure content browser warnings. For example, instead of:
StaticWebPath http://www.example.com/path/to/mt-static/
You can use:
StaticWebPath /path/to/mt-static/
Or even:
StaticWebPath //www.example.com/path/to/mt-static/
