from http to https after installation?

Discussion in 'Installation/Configuration' started by Mahir, Nov 5, 2005.

  1. Mahir

    Mahir New Member


    I have a ispconfig server running atm it is running on http but now we wanne run it on https how must we do this? because we already have domain names running on this server? is there anyway to change to to https://name:81 ?

  2. domino

    domino New Member

    Off hand I don't remember where the link is. But there is a post here where you can change https to http. Maybe you'll find it and perform the instructions backwards.
  3. falko

    falko Super Moderator

    You can do it like this: in the ISPConfig tarball, after you've unpacked it, there's a file httpd.conf_https. Copy it to /root/ispconfig/httpd/conf and rename it to httpd.conf (make a backup of the current httpd.conf before!). Then open the new httpd.conf and replace {SERVER_NAME} with the server name (have a look at the backed-up httpd.conf to find out the correct value).
    Then open /home/admispconfig/ispconfig/lib/ and change the ISPConfig URL from http to https.
    Finally restart ISPConfig:
    /etc/init.d/ispconfig_server restart
  4. Mahir

    Mahir New Member

    Ok thank u will try this out in the morning :)
  5. drbista

    drbista New Member

    Some http and some https, how?

    Dear Falko:

    This instruction seems to make the entire site in SSL, yes? Let me say if I want to make some component of the site http and some https (like webmail, ispconfig, phpmyadmin etc.). Does the same instruction apply for that, please elaborate. Thanks!
  6. till

    till Super Moderator

    What do you mean with "entire site in SSL". On the ISPConfig apache are only the ispconfig webinterface, phpmyadmin and webmail hosted.
  7. falko

    falko Super Moderator

    You seem to mix up the ISPConfig Apache and the main Apache! These are two completely independent servers! You can run ISPConfig, phpMyAdmin and webmail on https with the instructions from above, and will have no effect on your regular web sites.
  8. Rocky

    Rocky New Member

    I have untar the ISPConfig-2.1.0.tar.gz file and cd into the install_ispconfig but cannot find the https.conf_https file. Is this the right path to look for the file?
  9. till

    till Super Moderator

    The file is in the directory:

  10. Rocky

    Rocky New Member

    I've done the above to get my server config to work using ssl but had no luck. I'm running the perfect debian and couldn't get this to work from the beginning. All it says is the page cannot be displayed. But when I go to, it says this server is running ssl and i need to use https. Any reason why this is not working?
    I've compared the 2 httpd.conf files and both have the same server name. I made sure that the server url is set to use https.
  11. falko

    falko Super Moderator

    Did you do this?

  12. Rocky

    Rocky New Member

    Yes, i did everything as the instructions said.
  13. falko

    falko Super Moderator

    Can you see anything in the logs in /root/ispconfig/httpd/logs?
  14. Rocky

    Rocky New Member

    Below are the contents of my ispconfig log files.

    access_log - - [06/Dec/2005:20:26:37 -0500] "GET /mod_ssl:error:HTTP-request HTTP/1.0" 400 520 - - [06/Dec/2005:20:26:43 -0500] "GET /mod_ssl:error:HTTP-request HTTP/1.0" 400 520 - - [06/Dec/2005:20:26:56 -0500] "GET /mod_ssl:error:HTTP-request HTTP/1.0" 400 520

    [Tue Dec 6 20:26:08 2005] [notice] Apache/1.3.33 (Unix) PHP/5.0.4 mod_ssl/2.8.23 OpenSSL/0.9.8 configured -- resuming normal
    [Tue Dec 6 20:26:08 2005] [notice] Accept mutex: sysvsem (Default: sysvsem)
    [Tue Dec 6 20:26:37 2005] [error] mod_ssl: SSL handshake failed: HTTP spoken on HTTPS port; trying to send HTML error page (
    OpenSSL library error follows)
    [Tue Dec 6 20:26:37 2005] [error] OpenSSL: error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request [Hint: speaking H
    TTP to HTTPS port!?]
    [Tue Dec 6 20:26:43 2005] [error] mod_ssl: SSL handshake failed: HTTP spoken on HTTPS port; trying to send HTML error page (
    OpenSSL library error follows)
    [Tue Dec 6 20:26:43 2005] [error] OpenSSL: error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request [Hint: speaking H
    TTP to HTTPS port!?]
    [Tue Dec 6 20:26:56 2005] [error] mod_ssl: SSL handshake failed: HTTP spoken on HTTPS port; trying to send HTML error page (
    OpenSSL library error follows)
    [Tue Dec 6 20:26:56 2005] [error] OpenSSL: error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request [Hint: speaking H
    TTP to HTTPS port!?]

    [06/Dec/2005 20:26:07 04966] [info] Server: Apache/1.3.33, Interface: mod_ssl/2.8.23, Library: OpenSSL/0.9.8
    [06/Dec/2005 20:26:07 04966] [info] Init: 1st startup round (still not detached)
    [06/Dec/2005 20:26:07 04966] [info] Init: Initializing OpenSSL library
    [06/Dec/2005 20:26:07 04966] [info] Init: Loading certificate & private key of SSL-aware server
    [06/Dec/2005 20:26:07 04966] [info] Init: Seeding PRNG with 136 bytes of entropy
    [06/Dec/2005 20:26:07 04966] [info] Init: Generating temporary RSA private keys (512/1024 bits)
    [06/Dec/2005 20:26:08 04966] [info] Init: Configuring temporary DH parameters (512/1024 bits)
    [06/Dec/2005 20:26:08 04967] [info] Init: 2nd startup round (already detached)
    [06/Dec/2005 20:26:08 04967] [info] Init: Reinitializing OpenSSL library
    [06/Dec/2005 20:26:08 04967] [info] Init: Seeding PRNG with 136 bytes of entropy
    [06/Dec/2005 20:26:08 04967] [info] Init: Configuring temporary RSA private keys (512/1024 bits)
    [06/Dec/2005 20:26:08 04967] [info] Init: Configuring temporary DH parameters (512/1024 bits)
    [06/Dec/2005 20:26:08 04967] [info] Init: Initializing (virtual) servers for SSL
    [06/Dec/2005 20:26:08 04967] [info] Init: Configuring server for SSL protocol
    [06/Dec/2005 20:26:08 04967] [warn] Init: ( RSA server certificate CommonName (CN) `Tech4You' does NOT match
    server name!?
    [06/Dec/2005 20:26:35 04979] [info] Connection to child 0 established (server, client
    [06/Dec/2005 20:26:35 04979] [info] Seeding PRNG with 1160 bytes of entropy
    [06/Dec/2005 20:26:35 04979] [info] Connection: Client IP:, Protocol: SSLv3, Cipher: RC4-MD5 (128/128 bits)
    [06/Dec/2005 20:26:36 04979] [info] Connection to child 0 closed with standard shutdown (server, client 68.8
    [06/Dec/2005 20:26:37 05149] [info] Connection to child 1 established (server, client
    [06/Dec/2005 20:26:37 05149] [info] Seeding PRNG with 1160 bytes of entropy
    [06/Dec/2005 20:26:37 05149] [error] SSL handshake failed: HTTP spoken on HTTPS port; trying to send HTML error page (OpenSSL
    library error follows)
    [06/Dec/2005 20:26:37 05149] [error] OpenSSL: error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request [Hint: speaking
    HTTP to HTTPS port!?]
    [06/Dec/2005 20:26:43 04979] [info] Connection to child 0 established (server, client
    [06/Dec/2005 20:26:43 04979] [info] Seeding PRNG with 1160 bytes of entropy
    [06/Dec/2005 20:26:43 04979] [error] SSL handshake failed: HTTP spoken on HTTPS port; trying to send HTML error page (OpenSSL
    library error follows)
    [06/Dec/2005 20:26:43 04979] [error] OpenSSL: error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request [Hint: speaking
    HTTP to HTTPS port!?]
    [06/Dec/2005 20:26:55 05149] [info] Connection to child 1 established (server, client
    [06/Dec/2005 20:26:55 05149] [info] Seeding PRNG with 1160 bytes of entropy
    [06/Dec/2005 20:26:55 05149] [info] Connection: Client IP:, Protocol: SSLv3, Cipher: RC4-MD5 (128/128 bits)
    [06/Dec/2005 20:26:55 05149] [info] Connection to child 1 closed with standard shutdown (server, client 68.8
    [06/Dec/2005 20:26:56 04979] [info] Connection to child 0 established (server, client
    [06/Dec/2005 20:26:56 04979] [info] Seeding PRNG with 1160 bytes of entropy
    [06/Dec/2005 20:26:56 04979] [error] SSL handshake failed: HTTP spoken on HTTPS port; trying to send HTML error page (OpenSSL
    library error follows)
    [06/Dec/2005 20:26:56 04979] [error] OpenSSL: error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request [Hint: speaking
    HTTP to HTTPS port!?]
    [06/Dec/2005 20:26:58 05149] [info] Connection to child 1 established (server, client
    [06/Dec/2005 20:26:58 05149] [info] Seeding PRNG with 1160 bytes of entropy
    [06/Dec/2005 20:26:58 05149] [info] Connection: Client IP:, Protocol: SSLv3, Cipher: RC4-MD5 (128/128 bits)
    [06/Dec/2005 20:26:58 05149] [info] Connection to child 1 closed with standard shutdown (server, client 68.8
    [06/Dec/2005 20:26:58 04979] [info] Connection to child 0 established (server, client
    [06/Dec/2005 20:26:58 04979] [info] Seeding PRNG with 1160 bytes of entropy
    [06/Dec/2005 20:26:58 04979] [info] Connection: Client IP:, Protocol: SSLv3, Cipher: RC4-MD5 (128/128 bits)
    [06/Dec/2005 20:26:58 04979] [info] Connection to child 0 closed with standard shutdown (server, client 68.8

    [06/Dec/2005:20:26:37 -0500] - - "GET /mod_ssl:error:HTTP-request HTTP/1.0" 520
    [06/Dec/2005:20:26:43 -0500] - - "GET /mod_ssl:error:HTTP-request HTTP/1.0" 520
    [06/Dec/2005:20:26:56 -0500] - - "GET /mod_ssl:error:HTTP-request HTTP/1.0" 520
  15. falko

    falko Super Moderator

    Are you really sure you replaced the httpd.conf with httpd.conf_https and restart ISPConfig afterwards?
  16. Rocky

    Rocky New Member

    Yes I did everything as you said.

    I first went into the /root/ispconfig/httpd/conf folder and made a copy, using the cp command, of httpd.conf to httpd.conf1.
    I then went into the extracted folder, install_ispconfig/compile_aps/, and did mv -i httpd.conf_https /root/ispconfig/httpd/conf/httpd.conf. It asked me if i wanted to overwrite the file and i said yes.
    I then switched directories to the /root/ispconfig/httpd/conf/ directory and did vi httpd.conf and changed everything that had {SERVER_NAME} to my server name.
    After that, i did vi home/admispconfig/ispconfig/lib/ and changed the server url to
    I then restarted ispconfig by running the command /etc/init.d/ispconfig_server restart.
    I think i followed your instructions properly but i'm not too sure about the commands i used.

    When i tried to access the server on https, prior to doing the above, it would just say that the page cannot be displayed. But it would take me to the login screen if i used http.
    Now, after the above, when i try to access the page using http, it says that the server is ssl enabled and i should use https. But when i try to use https, it give me the error saying that the page cannot be displayed.

    Im not sure whats going on or if my server is functioning properly.
  17. falko

    falko Super Moderator

    Can you post /root/ispconfig/httpd/conf/httpd.conf here?
  18. Rocky

    Rocky New Member

    Here it is.
    ## httpd.conf -- Apache HTTP server configuration file

    # Based upon the NCSA server configuration files originally by Rob McCool.
    # This is the main Apache server configuration file. It contains the
    # configuration directives that give the server its instructions.
    # See <URL:> for detailed information about
    # the directives.
    # Do NOT simply read the instructions in here without understanding
    # what they do. They're here only as hints or reminders. If you are unsure
    # consult the online docs. You have been warned.
    # After this file is processed, the server will look for and process
    # /root/ispconfig/httpd/conf/srm.conf and then /root/ispconfig/httpd/conf/access.conf
    # unless you have overridden these with ResourceConfig and/or
    # AccessConfig directives here.
    # The configuration directives are grouped into three basic sections:
    # 1. Directives that control the operation of the Apache server process as a
    # whole (the 'global environment').
    # 2. Directives that define the parameters of the 'main' or 'default' server,
    # which responds to requests that aren't handled by a virtual host.
    # These directives also provide default values for the settings
    # of all virtual hosts.
    # 3. Settings for virtual hosts, which allow Web requests to be sent to
    # different IP addresses or hostnames and have them handled by the
    # same Apache server process.
    # Configuration and logfile names: If the filenames you specify for many
    # of the server's control files begin with "/" (or "drive:/" for Win32), the
    # server will use that explicit path. If the filenames do *not* begin
    # with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
    # with ServerRoot set to "/usr/local/apache" will be interpreted by the
    # server as "/usr/local/apache/logs/foo.log".

    ### Section 1: Global Environment
    # The directives in this section affect the overall operation of Apache,
    # such as the number of concurrent requests it can handle or where it
    # can find its configuration files.

    # ServerType is either inetd, or standalone. Inetd mode is only supported on
    # Unix platforms.
    ServerType standalone

    # ServerRoot: The top of the directory tree under which the server's
    # configuration, error, and log files are kept.
    # NOTE! If you intend to place this on an NFS (or otherwise network)
    # mounted filesystem then please read the LockFile documentation
    # (available at <URL:>);
    # you will save yourself a lot of trouble.
    ServerRoot "/root/ispconfig/httpd"

    # The LockFile directive sets the path to the lockfile used when Apache
    # is compiled with either USE_FCNTL_SERIALIZED_ACCEPT or
    # USE_FLOCK_SERIALIZED_ACCEPT. This directive should normally be left at
    # its default value. The main reason for changing it is if the logs
    # directory is NFS mounted, since the lockfile MUST BE STORED ON A LOCAL
    # DISK. The PID of the main server process is automatically appended to
    # the filename.
    #LockFile /root/ispconfig/httpd/logs/httpd.lock

    # PidFile: The file in which the server should record its process
    # identification number when it starts.
    PidFile /root/ispconfig/httpd/logs/

    # ScoreBoardFile: File used to store internal server process information.
    # Not all architectures require this. But if yours does (you'll know because
    # this file will be created when you run Apache) then you *must* ensure that
    # no two invocations of Apache share the same scoreboard file.
    ScoreBoardFile /root/ispconfig/httpd/logs/httpd.scoreboard
    # In the standard configuration, the server will process httpd.conf (this
    # file, specified by the -f command line option), srm.conf, and access.conf
    # in that order. The latter two files are now distributed empty, as it is
    # recommended that all directives be kept in a single file for simplicity.
    # The commented-out values below are the built-in defaults. You can have the
    # server ignore these files altogether by using "/dev/null" (for Unix) or
    # "nul" (for Win32) for the arguments to the directives.
    #ResourceConfig conf/srm.conf
    #AccessConfig conf/access.conf

    # Timeout: The number of seconds before receives and sends time out.
    Timeout 300

    # KeepAlive: Whether or not to allow persistent connections (more than
    # one request per connection). Set to "Off" to deactivate.
    KeepAlive On

    # MaxKeepAliveRequests: The maximum number of requests to allow
    # during a persistent connection. Set to 0 to allow an unlimited amount.
    # We recommend you leave this number high, for maximum performance.
    MaxKeepAliveRequests 100

    # KeepAliveTimeout: Number of seconds to wait for the next request from the
    # same client on the same connection.
    KeepAliveTimeout 15

    # Server-pool size regulation. Rather than making you guess how many
    # server processes you need, Apache dynamically adapts to the load it
    # sees --- that is, it tries to maintain enough server processes to
    # handle the current load, plus a few spare servers to handle transient
    # load spikes (e.g., multiple simultaneous requests from a single
    # Netscape browser).
    # It does this by periodically checking how many servers are waiting
    # for a request. If there are fewer than MinSpareServers, it creates
    # a new spare. If there are more than MaxSpareServers, some of the
    # spares die off. The default values are probably OK for most sites.
    MinSpareServers 1
    MaxSpareServers 1

    # Number of servers to start initially --- should be a reasonable ballpark
    # figure.
    StartServers 1

    # Limit on total number of servers running, i.e., limit on the number
    # of clients who can simultaneously connect --- if this limit is ever
    # reached, clients will be LOCKED OUT, so it should NOT BE SET TOO LOW.
    # It is intended mainly as a brake to keep a runaway server from taking
    # the system with it as it spirals down...
    MaxClients 150

    # MaxRequestsPerChild: the number of requests each child process is
    # allowed to process before the child dies. The child will exit so
    # as to avoid problems after prolonged use when Apache (and maybe the
    # libraries it uses) leak memory or other resources. On most systems, this
    # isn't really needed, but a few (such as Solaris) do have notable leaks
    # in the libraries. For these platforms, set to something like 10000
    # or so; a setting of 0 means unlimited.
    # NOTE: This value does not include keepalive requests after the initial
    # request per connection. For example, if a child process handles
    # an initial request and 10 subsequent "keptalive" requests, it
    # would only count as 1 request towards this limit.
    MaxRequestsPerChild 0

    # Listen: Allows you to bind Apache to specific IP addresses and/or
    # ports, in addition to the default. See also the <VirtualHost>
    # directive.
    #Listen 3000

    # BindAddress: You can support virtual hosts with this option. This directive
    # is used to tell the server which IP address to listen to. It can either
    # contain "*", an IP address, or a fully qualified Internet domain name.
    # See also the <VirtualHost> and Listen directives.
    #BindAddress *

    # Dynamic Shared Object (DSO) Support
    # To be able to use the functionality of a module which was built as a DSO you
    # have to place corresponding `LoadModule' lines at this location so the
    # directives contained in it are actually available _before_ they are used.
    # Please read the file for more
    # details about the DSO mechanism and run `httpd -l' for the list of already
    # built-in (statically linked and thus always available) modules in your httpd
    # binary.
    # Note: The order in which modules are loaded is important. Don't change
    # the order below without expert advice.
    # Example:
    # LoadModule foo_module libexec/
    LoadModule php5_module libexec/

    # ExtendedStatus controls whether Apache will generate "full" status
    # information (ExtendedStatus On) or just basic information (ExtendedStatus
    # Off) when the "server-status" handler is called. The default is Off.
    #ExtendedStatus On

    ### Section 2: 'Main' server configuration
    # The directives in this section set up the values used by the 'main'
    # server, which responds to any requests that aren't handled by a
    # <VirtualHost> definition. These values also provide defaults for
    # any <VirtualHost> containers you may define later in the file.
    # All of these directives may appear inside <VirtualHost> containers,
    # in which case these default settings will be overridden for the
    # virtual host being defined.

    # If your ServerType directive (set earlier in the 'Global Environment'
    # section) is set to "inetd", the next few directives don't have any
    # effect since their settings are defined by the inetd configuration.
    # Skip ahead to the ServerAdmin directive.

    # Port: The port to which the standalone server listens. For
    # ports < 1023, you will need httpd to be run as root initially.
    Port 81
    Last edited: Dec 7, 2005
  19. Rocky

    Rocky New Member

    ## SSL Support
    ## When we also provide SSL we have to listen to the
    ## standard HTTP port (see above) and to the HTTPS port
    <IfDefine SSL>
    Listen 81

    # If you wish httpd to run as a different user or group, you must run
    # httpd as root initially and it will switch.
    # User/Group: The name (or #number) of the user/group to run httpd as.
    # . On SCO (ODT 3) use "User nouser" and "Group nogroup".
    # . On HPUX you may not be able to use shared memory as nobody, and the
    # suggested workaround is to create a user www and use that user.
    # NOTE that some kernels refuse to setgid(Group) or semctl(IPC_SET)
    # when the value of (unsigned)Group is above 60000;
    # don't use Group nobody on these systems!
    User admispconfig
    Group admispconfig
    # ServerAdmin: Your address, where problems with the server should be
    # e-mailed. This address appears on some server-generated pages, such
    # as error documents.

    # ServerName allows you to set a host name which is sent back to clients for
    # your server if it's different than the one the program would get (i.e., use
    # "www" instead of the host's real name).
    # Note: You cannot just invent host names and hope they work. The name you
    # define here must be a valid DNS name for your host. If you don't understand
    # this, ask your network administrator.
    # If your host doesn't have a registered DNS name, enter its IP address here.
    # You will have to access it by its address (e.g.,
    # anyway, and this will make redirections work in a sensible way.
    # is the TCP/IP local loop-back address, often named localhost. Your
    # machine always knows itself by this address. If you use Apache strictly for
    # local testing and development, you may use as the server name.

    # DocumentRoot: The directory out of which you will serve your
    # documents. By default, all requests are taken from this directory, but
    # symbolic links and aliases may be used to point to other locations.
    DocumentRoot "/home/admispconfig/ispconfig/web"

    # Each directory to which Apache has access, can be configured with respect
    # to which services and features are allowed and/or disabled in that
    # directory (and its subdirectories).
    # First, we configure the "default" to be a very restrictive set of
    # permissions.
    <Directory />
    Options FollowSymLinks
    AllowOverride None

    # Note that from this point forward you must specifically allow
    # particular features to be enabled - so if something's not working as
    # you might expect, make sure that you have specifically enabled it
    # below.

    # This should be changed to whatever you set DocumentRoot to.
    <Directory "/home/admispconfig/ispconfig/web">

    # This may also be "None", "All", or any combination of "Indexes",
    # "Includes", "FollowSymLinks", "ExecCGI", or "MultiViews".
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    Options Indexes FollowSymLinks MultiViews

    # This controls which options the .htaccess files in directories can
    # override. Can also be "All", or any combination of "Options", "FileInfo",
    # "AuthConfig", and "Limit"
    AllowOverride None

    # Controls who can get stuff from this server.
    Order allow,deny
    Allow from all

    # UserDir: The name of the directory which is appended onto a user's home
    # directory if a ~user request is received.
    <IfModule mod_userdir.c>
    UserDir public_html

    # Control access to UserDir directories. The following is an example
    # for a site where these directories are restricted to read-only.
    #<Directory /home/*/public_html>
    # AllowOverride FileInfo AuthConfig Limit
    # Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
    # Order allow,deny
    # Allow from all
    # </Limit>
    # Order deny,allow
    # Deny from all
    # </LimitExcept>

    # DirectoryIndex: Name of the file or files to use as a pre-written HTML
    # directory index. Separate multiple entries with spaces.
    <IfModule mod_dir.c>
    DirectoryIndex index.html index.php

    # AccessFileName: The name of the file to look for in each directory
    # for access control information.
    AccessFileName .htaccess

    # The following lines prevent .htaccess files from being viewed by
    # Web clients. Since .htaccess files often contain authorization
    # information, access is disallowed for security reasons. Comment
    # these lines out if you want Web visitors to see the contents of
    # .htaccess files. If you change the AccessFileName directive above,
    # be sure to make the corresponding changes here.
    # Also, folks tend to use names such as .htpasswd for password
    # files, so this will protect those as well.
    <Files ~ "^\.ht">
    Order allow,deny
    Deny from all
    Satisfy All

    # CacheNegotiatedDocs: By default, Apache sends "Pragma: no-cache" with each
    # document that was negotiated on the basis of content. This asks proxy
    # servers not to cache the document. Uncommenting the following line disables
    # this behavior, and proxies will be allowed to cache the documents.

    # UseCanonicalName: (new for 1.3) With this setting turned on, whenever
    # Apache needs to construct a self-referencing URL (a URL that refers back
    # to the server the response is coming from) it will use ServerName and
    # Port to form a "canonical" name. With this setting off, Apache will
    # use the hostname:port that the client supplied, when possible. This
    # also affects SERVER_NAME and SERVER_PORT in CGI scripts.
    UseCanonicalName On

    # TypesConfig describes where the mime.types file (or equivalent) is
    # to be found.
    <IfModule mod_mime.c>
    TypesConfig /root/ispconfig/httpd/conf/mime.types

    # DefaultType is the default MIME type the server will use for a document
    # if it cannot otherwise determine one, such as from filename extensions.
    # If your server contains mostly text or HTML documents, "text/plain" is
    # a good value. If most of your content is binary, such as applications
    # or images, you may want to use "application/octet-stream" instead to
    # keep browsers from trying to display binary files as though they are
    # text.
    DefaultType text/plain

    # The mod_mime_magic module allows the server to use various hints from the
    # contents of the file itself to determine its type. The MIMEMagicFile
    # directive tells the module where the hint definitions are located.
    # mod_mime_magic is not part of the default server (you have to add
    # it yourself with a LoadModule [see the DSO paragraph in the 'Global
    # Environment' section], or recompile the server and include mod_mime_magic
    # as part of the configuration), so it's enclosed in an <IfModule> container.
    # This means that the MIMEMagicFile directive will only be processed if the
    # module is part of the server.
    <IfModule mod_mime_magic.c>
    MIMEMagicFile /root/ispconfig/httpd/conf/magic

    # HostnameLookups: Log the names of clients or just their IP addresses
    # e.g., (on) or (off).
    # The default is off because it'd be overall better for the net if people
    # had to knowingly turn this feature on, since enabling it means that
    # each client request will result in AT LEAST one lookup request to the
    # nameserver.
    HostnameLookups Off

    # ErrorLog: The location of the error log file.
    # If you do not specify an ErrorLog directive within a <VirtualHost>
    # container, error messages relating to that virtual host will be
    # logged here. If you *do* define an error logfile for a <VirtualHost>
    # container, that host's errors will be logged there and not here.
    ErrorLog /root/ispconfig/httpd/logs/error_log

    # LogLevel: Control the number of messages logged to the error_log.
    # Possible values include: debug, info, notice, warn, error, crit,
    # alert, emerg.
    LogLevel warn

    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common
    LogFormat "%{Referer}i -> %U" referer
    LogFormat "%{User-agent}i" agent

    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here. Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    CustomLog /root/ispconfig/httpd/logs/access_log common

    # If you would like to have agent and referer logfiles, uncomment the
    # following directives.
    #CustomLog /root/ispconfig/httpd/logs/referer_log referer
    #CustomLog /root/ispconfig/httpd/logs/agent_log agent

    # If you prefer a single logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #CustomLog /root/ispconfig/httpd/logs/access_log combined

    # Optionally add a line containing the server version and virtual host
    # name to server-generated pages (error documents, FTP directory listings,
    # mod_status and mod_info output etc., but not CGI generated documents).
    # Set to "EMail" to also include a mailto: link to the ServerAdmin.
    # Set to one of: On | Off | EMail
    ServerSignature On
  20. Rocky

    Rocky New Member

    # EBCDIC configuration:
    # (only for mainframes using the EBCDIC codeset, currently one of:
    # Fujitsu-Siemens' BS2000/OSD, IBM's OS/390 and IBM's TPF)!!
    # The following default configuration assumes that "text files"
    # are stored in EBCDIC (so that you can operate on them using the
    # normal POSIX tools like grep and sort) while "binary files" are
    # stored with identical octets as on an ASCII machine.
    # The directives are evaluated in configuration file order, with
    # the EBCDICConvert directives applied before EBCDICConvertByType.
    # If you want to have ASCII HTML documents and EBCDIC HTML documents
    # at the same time, you can use the file extension to force
    # conversion off for the ASCII documents:
    # > AddType text/html .ahtml
    # > EBCDICConvert Off=InOut .ahtml
    # EBCDICConvertByType On=InOut text/* message/* multipart/*
    # EBCDICConvertByType On=In application/x-www-form-urlencoded
    # EBCDICConvertByType On=InOut application/postscript model/vrml
    # EBCDICConvertByType Off=InOut */*

    # Aliases: Add here as many aliases as you need (with no limit). The format is
    # Alias fakename realname
    <IfModule mod_alias.c>

    # Note that if you include a trailing / on fakename then the server will
    # require it to be present in the URL. So "/icons" isn't aliased in this
    # example, only "/icons/". If the fakename is slash-terminated, then the
    # realname must also be slash terminated, and if the fakename omits the
    # trailing slash, the realname must also omit it.
    Alias /icons/ "/root/ispconfig/httpd/icons/"

    <Directory "/root/ispconfig/httpd/icons">
    Options Indexes MultiViews
    AllowOverride None
    Order allow,deny
    Allow from all

    # This Alias will project the on-line documentation tree under /manual/
    # even if you change the DocumentRoot. Comment it if you don't want to
    # provide access to the on-line documentation.
    Alias /manual/ "/root/ispconfig/httpd/htdocs/manual/"

    <Directory "/root/ispconfig/httpd/htdocs/manual">
    Options Indexes FollowSymlinks MultiViews
    AllowOverride None
    Order allow,deny
    Allow from all

    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the realname directory are treated as applications and
    # run by the server when requested rather than as documents sent to the client.
    # The same rules about trailing "/" apply to ScriptAlias directives as to
    # Alias.
    ScriptAlias /cgi-bin/ "/root/ispconfig/httpd/cgi-bin/"

    # "/root/ispconfig/httpd/cgi-bin" should be changed to whatever your ScriptAliased
    # CGI directory exists, if you have that configured.
    <Directory "/root/ispconfig/httpd/cgi-bin">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all

    # End of aliases.

    # Redirect allows you to tell clients about documents which used to exist in
    # your server's namespace, but do not anymore. This allows you to tell the
    # clients where to look for the relocated document.
    # Format: Redirect old-URI new-URL

    # Directives controlling the display of server-generated directory listings.
    <IfModule mod_autoindex.c>

    # FancyIndexing is whether you want fancy directory indexing or standard
    IndexOptions FancyIndexing

    # AddIcon* directives tell the server which icon to show for different
    # files or filename extensions. These are only displayed for
    # FancyIndexed directories.
    AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip

    AddIconByType (TXT,/icons/text.gif) text/*
    AddIconByType (IMG,/icons/image2.gif) image/*
    AddIconByType (SND,/icons/sound2.gif) audio/*
    AddIconByType (VID,/icons/movie.gif) video/*

    AddIcon /icons/binary.gif .bin .exe
    AddIcon /icons/binhex.gif .hqx
    AddIcon /icons/tar.gif .tar
    AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv
    AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip
    AddIcon /icons/a.gif .ps .ai .eps
    AddIcon /icons/layout.gif .html .shtml .htm .pdf
    AddIcon /icons/text.gif .txt
    AddIcon /icons/c.gif .c
    AddIcon /icons/p.gif .pl .py
    AddIcon /icons/f.gif .for
    AddIcon /icons/dvi.gif .dvi
    AddIcon /icons/uuencoded.gif .uu
    AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl
    AddIcon /icons/tex.gif .tex
    AddIcon /icons/bomb.gif core

    AddIcon /icons/back.gif ..
    AddIcon /icons/hand.right.gif README
    AddIcon /icons/folder.gif ^^DIRECTORY^^
    AddIcon /icons/blank.gif ^^BLANKICON^^
    # DefaultIcon is which icon to show for files which do not have an icon
    # explicitly set.
    DefaultIcon /icons/unknown.gif

    # AddDescription allows you to place a short description after a file in
    # server-generated indexes. These are only displayed for FancyIndexed
    # directories.
    # Format: AddDescription "description" filename
    #AddDescription "GZIP compressed document" .gz
    #AddDescription "tar archive" .tar
    #AddDescription "GZIP compressed tar archive" .tgz

    # ReadmeName is the name of the README file the server will look for by
    # default, and append to directory listings.
    # HeaderName is the name of a file which should be prepended to
    # directory indexes.
    # If MultiViews are amongst the Options in effect, the server will
    # first look for name.html and include it if found. If name.html
    # doesn't exist, the server will then look for name.txt and include
    # it as plaintext if found.
    ReadmeName README
    HeaderName HEADER

    # IndexIgnore is a set of filenames which directory indexing should ignore
    # and not include in the listing. Shell-style wildcarding is permitted.
    IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t

    # End of indexing directives.

    # Document types.
    <IfModule mod_mime.c>

    # AddEncoding allows you to have certain browsers (Mosaic/X 2.1+) uncompress
    # information on the fly. Note: Not all browsers support this.
    # Despite the name similarity, the following Add* directives have nothing
    # to do with the FancyIndexing customization directives above.
    AddEncoding x-compress Z
    AddEncoding x-gzip gz tgz

    # AddLanguage allows you to specify the language of a document. You can
    # then use content negotiation to give a browser a file in a language
    # it can understand.
    # Note 1: The suffix does not have to be the same as the language
    # keyword --- those with documents in Polish (whose net-standard
    # language code is pl) may wish to use "AddLanguage pl .po" to
    # avoid the ambiguity with the common suffix for perl scripts.
    # Note 2: The example entries below illustrate that in quite
    # some cases the two character 'Language' abbreviation is not
    # identical to the two character 'Country' code for its country,
    # E.g. 'Danmark/dk' versus 'Danish/da'.
    # Note 3: In the case of 'ltz' we violate the RFC by using a three char
    # specifier. But there is 'work in progress' to fix this and get
    # the reference data for rfc1766 cleaned up.
    # Danish (da) - Dutch (nl) - English (en) - Estonian (ee)
    # French (fr) - German (de) - Greek-Modern (el)
    # Italian (it) - Korean (kr) - Norwegian (no) - Norwegian Nynorsk (nn)
    # Portugese (pt) - Luxembourgeois* (ltz)
    # Spanish (es) - Swedish (sv) - Catalan (ca) - Czech(cz)
    # Polish (pl) - Brazilian Portuguese (pt-br) - Japanese (ja)
    # Russian (ru)
    AddLanguage da .dk
    AddLanguage nl .nl
    AddLanguage en .en
    AddLanguage et .ee
    AddLanguage fr .fr
    AddLanguage de .de
    AddLanguage el .el
    AddLanguage he .he
    AddCharset ISO-8859-8 .iso8859-8
    AddLanguage it .it
    AddLanguage ja .ja
    AddCharset ISO-2022-JP .jis
    AddLanguage kr .kr
    AddCharset ISO-2022-KR .iso-kr
    AddLanguage nn .nn
    AddLanguage no .no
    AddLanguage pl .po
    AddCharset ISO-8859-2 .iso-pl
    AddLanguage pt .pt
    AddLanguage pt-br .pt-br
    AddLanguage ltz .lu
    AddLanguage ca .ca
    AddLanguage es .es
    AddLanguage sv .sv
    AddLanguage cz .cz
    AddLanguage ru .ru
    AddLanguage zh-tw .tw
    AddLanguage tw .tw
    AddCharset Big5 .Big5 .big5
    AddCharset WINDOWS-1251 .cp-1251
    AddCharset CP866 .cp866
    AddCharset ISO-8859-5 .iso-ru
    AddCharset KOI8-R .koi8-r
    AddCharset UCS-2 .ucs2
    AddCharset UCS-4 .ucs4
    AddCharset UTF-8 .utf8

Share This Page