1. Apache2 & Openssl

    Date: 11/26/06 (Apache)    Keywords: browser, html, apache

    Ok I have Apache2 and openssl working -- mostly.  Apache starts without issue, and when I go to localhost:443 I have a little lock in my address bar.  My problem is that files in my 'secure' htdocs folder (as specified in ssl.conf) do not exist, according to apache.

    I've never installed a secure server so I may be missing something obvious - any help with this is greatly appreciated.

    Config files beneath the cut:


    SSL.CONF
    #
    # This is the Apache server configuration file providing SSL support.
    # It contains the configuration directives to instruct the server how to
    # serve pages over an https connection. For detailing information about these
    # directives see
    #
    #  For the moment, see for this info.
    #  The documents are still being prepared from material donated by the
    #  modssl project.
    #
    # 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. 
    #

    #

    #  Until documentation is completed, please check http://www.modssl.org/
    #  for additional config examples and module docmentation.  Directives
    #  and features of mod_ssl are largely unchanged from the mod_ssl project
    #  for Apache 1.3.

    #
    # When we also provide SSL we have to listen to the
    # standard HTTP port (see above) and to the HTTPS port
    #
    Listen 443

    #
    # Dynamic Shared Object (DSO) Support
    #
    # To be able to use the functionality of a module which was built as a DSO you
    #    ErrorLog logs/dummy-host.example.com-error_log
    #    CustomLog logs/dummy-host.example.com-access_log common

    ##
    ##  SSL Global Context
    ##
    ##  All SSL configuration in this context applies both to
    ##  the main server and all SSL-enabled virtual hosts.
    ##

    #
    #  Some MIME-types for downloading Certificates and CRLs
    #
    AddType application/x-x509-ca-cert .crt
    AddType application/x-pkcs7-crl    .crl

    #  Pass Phrase Dialog:
    #  Configure the pass phrase gathering process.
    #  The filtering dialog program (`builtin' is a internal
    #  terminal dialog) has to provide the pass phrase on stdout.
    SSLPassPhraseDialog  builtin

    #  Inter-Process Session Cache:
    #  Configure the SSL Session Cache: First the mechanism
    #  to use and second the expiring timeout (in seconds).
    #SSLSessionCache        none
    #SSLSessionCache        shmht:logs/ssl_scache(512000)
    #SSLSessionCache        shmcb:logs/ssl_scache(512000)
    SSLSessionCache        dbm:logs/ssl-scache.log
    SSLSessionCacheTimeout  300

    #  Semaphore:
    #  Configure the path to the mutual exclusion semaphore the
    #  SSL engine uses internally for inter-process synchronization.
    #SSLMutex  file:logs/ssl_mutex.log
    SSLMutex default

    #  Pseudo Random Number Generator (PRNG):
    #  Configure one or more sources to seed the PRNG of the
    #  SSL library. The seed data should be of good random quality.
    #  WARNING! On some platforms /dev/random blocks if not enough entropy
    #  is available. This means you then cannot use the /dev/random device
    #  because it would lead to very long connection times (as long as
    #  it requires to make more entropy available). But usually those
    #  platforms additionally provide a /dev/urandom device which doesn't
    #  block. So, if available, use this one instead. Read the mod_ssl User
    #  Manual for more details.
    SSLRandomSeed startup builtin
    SSLRandomSeed connect builtin
    #SSLRandomSeed startup file:/dev/random  512
    #SSLRandomSeed startup file:/dev/urandom 512
    #SSLRandomSeed connect file:/dev/random  512
    #SSLRandomSeed connect file:/dev/urandom 512

    ##
    ## SSL Virtual Host Context
    ##



    #  General setup for the virtual host
    DocumentRoot "C:\Program Files\Apache Group\Apache2\htdocs_secure"
    ServerName localhost:443
    #ServerName www.my-domain.com:443
    ServerAdmin you@your.address
    ErrorLog logs/error.log
    TransferLog logs/access.log

    #  SSL Engine Switch:
    #  Enable/Disable SSL for this virtual host.
    SSLEngine on

    #  SSL Cipher Suite:
    #  List the ciphers that the client is permitted to negotiate.
    #  See the mod_ssl documentation for a complete list.
    SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL

    #  Server Certificate:
    #  Point SSLCertificateFile at a PEM encoded certificate.  If
    #  the certificate is encrypted, then you will be prompted for a
    #  pass phrase.  Note that a kill -HUP will prompt again.  Keep
    #  in mind that if you have both an RSA and a DSA certificate you
    #  can configure both in parallel (to also allow the use of DSA
    #  ciphers, etc.)
    SSLCertificateFile conf/ssl/my-server.cert
    #SSLCertificateFile conf/ssl.crt/server-dsa.crt

    #  Server Private Key:
    #  If the key is not combined with the certificate, use this
    #  directive to point at the key file.  Keep in mind that if
    #  you've both a RSA and a DSA private key you can configure
    #  both in parallel (to also allow the use of DSA ciphers, etc.)
    SSLCertificateKeyFile conf/ssl/my-server.key
    #SSLCertificateKeyFile conf/ssl.key/server-dsa.key

    #  Server Certificate Chain:
    #  Point SSLCertificateChainFile at a file containing the
    #  concatenation of PEM encoded CA certificates which form the
    #  certificate chain for the server certificate. Alternatively
    #  the referenced file can be the same as SSLCertificateFile
    #  when the CA certificates are directly appended to the server
    #  certificate for convinience.
    #SSLCertificateChainFile conf/ssl.crt/ca.crt

    #  Certificate Authority (CA):
    #  Set the CA certificate verification path where to find CA
    #  certificates for client authentication or alternatively one
    #  huge file containing all of them (file must be PEM encoded)
    #  Note: Inside SSLCACertificatePath you need hash symlinks
    #        to point to the certificate files. Use the provided
    #        Makefile to update the hash symlinks after changes.
    #SSLCACertificatePath conf/ssl.crt
    #SSLCACertificateFile conf/ssl.crt/ca-bundle.crt

    #  Certificate Revocation Lists (CRL):
    #  Set the CA revocation path where to find CA CRLs for client
    #  authentication or alternatively one huge file containing all
    #  of them (file must be PEM encoded)
    #  Note: Inside SSLCARevocationPath you need hash symlinks
    #        to point to the certificate files. Use the provided
    #        Makefile to update the hash symlinks after changes.
    #SSLCARevocationPath conf/ssl.crl
    #SSLCARevocationFile conf/ssl.crl/ca-bundle.crl

    #  Client Authentication (Type):
    #  Client certificate verification type and depth.  Types are
    #  none, optional, require and optional_no_ca.  Depth is a
    #  number which specifies how deeply to verify the certificate
    #  issuer chain before deciding the certificate is not valid.
    #SSLVerifyClient require
    #SSLVerifyDepth  10

    #  Access Control:
    #  With SSLRequire you can do per-directory access control based
    #  on arbitrary complex boolean expressions containing server
    #  variable checks and other lookup directives.  The syntax is a
    #  mixture between C and Perl.  See the mod_ssl documentation
    #  for more details.
    #
    #SSLRequire (    %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
    #            and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
    #            and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
    #            and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
    #            and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20      ) \
    #          or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
    #


    #  SSL Engine Options:
    #  Set various options for the SSL engine.
    #  o FakeBasicAuth:
    #    Translate the client X.509 into a Basic Authorisation.  This means that
    #    the standard Auth/DBMAuth methods can be used for access control.  The
    #    user name is the `one line' version of the client's X.509 certificate.
    #    Note that no password is obtained from the user. Every entry in the user
    #    file needs this password: `xxj31ZMTZzkVA'.
    #  o ExportCertData:
    #    This exports two additional environment variables: SSL_CLIENT_CERT and
    #    SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
    #    server (always existing) and the client (only existing when client
    #    authentication is used). This can be used to import the certificates
    #    into CGI scripts.
    #  o StdEnvVars:
    #    This exports the standard SSL/TLS related `SSL_*' environment variables.
    #    Per default this exportation is switched off for performance reasons,
    #    because the extraction step is an expensive operation and is usually
    #    useless for serving static content. So one usually enables the
    #    exportation for CGI and SSI requests only.
    #  o CompatEnvVars:
    #    This exports obsolete environment variables for backward compatibility
    #    to Apache-SSL 1.x, mod_ssl 2.0.x, Sioux 1.0 and Stronghold 2.x. Use this
    #    to provide compatibility to existing CGI scripts.
    #  o StrictRequire:
    #    This denies access when "SSLRequireSSL" or "SSLRequire" applied even
    #    under a "Satisfy any" situation, i.e. when it applies access is denied
    #    and no other module can change it.
    #  o OptRenegotiate:
    #    This enables optimized SSL connection renegotiation handling when SSL
    #    directives are used in per-directory context.
    #SSLOptions +FakeBasicAuth +ExportCertData +CompatEnvVars +StrictRequire

    [Error: Irreparable invalid markup ('') in entry. Owner must fix manually. Raw contents below.]

    Ok I have Apache2 and openssl working -- mostly.&nbsp; Apache starts without issue, and when I go to localhost:443 I have a little lock in my address bar.&nbsp; My problem is that files in my 'secure' htdocs folder (as specified in ssl.conf) do not exist, according to apache.

    I've never installed a secure server so I may be missing something obvious - any help with this is greatly appreciated.

    Config files beneath the cut:


    SSL.CONF
    #
    # This is the Apache server configuration file providing SSL support.
    # It contains the configuration directives to instruct the server how to
    # serve pages over an https connection. For detailing information about these
    # directives see
    #
    #&nbsp; For the moment, see for this info.
    #&nbsp; The documents are still being prepared from material donated by the
    #&nbsp; modssl project.
    #
    # Do NOT simply read the instructions in here without understanding
    # what they do.&nbsp; They're here only as hints or reminders.&nbsp; If you are unsure
    # consult the online docs. You have been warned.&nbsp;
    #

    #

    #&nbsp; Until documentation is completed, please check http://www.modssl.org/
    #&nbsp; for additional config examples and module docmentation.&nbsp; Directives
    #&nbsp; and features of mod_ssl are largely unchanged from the mod_ssl project
    #&nbsp; for Apache 1.3.

    #
    # When we also provide SSL we have to listen to the
    # standard HTTP port (see above) and to the HTTPS port
    #
    Listen 443

    #
    # Dynamic Shared Object (DSO) Support
    #
    # To be able to use the functionality of a module which was built as a DSO you
    #&nbsp; &nbsp; ErrorLog logs/dummy-host.example.com-error_log
    #&nbsp; &nbsp; CustomLog logs/dummy-host.example.com-access_log common

    ##
    ##&nbsp; SSL Global Context
    ##
    ##&nbsp; All SSL configuration in this context applies both to
    ##&nbsp; the main server and all SSL-enabled virtual hosts.
    ##

    #
    #&nbsp; Some MIME-types for downloading Certificates and CRLs
    #
    AddType application/x-x509-ca-cert .crt
    AddType application/x-pkcs7-crl&nbsp; &nbsp; .crl

    #&nbsp; Pass Phrase Dialog:
    #&nbsp; Configure the pass phrase gathering process.
    #&nbsp; The filtering dialog program (`builtin' is a internal
    #&nbsp; terminal dialog) has to provide the pass phrase on stdout.
    SSLPassPhraseDialog&nbsp; builtin

    #&nbsp; Inter-Process Session Cache:
    #&nbsp; Configure the SSL Session Cache: First the mechanism
    #&nbsp; to use and second the expiring timeout (in seconds).
    #SSLSessionCache&nbsp; &nbsp; &nbsp; &nbsp; none
    #SSLSessionCache&nbsp; &nbsp; &nbsp; &nbsp; shmht:logs/ssl_scache(512000)
    #SSLSessionCache&nbsp; &nbsp; &nbsp; &nbsp; shmcb:logs/ssl_scache(512000)
    SSLSessionCache&nbsp; &nbsp; &nbsp; &nbsp; dbm:logs/ssl-scache.log
    SSLSessionCacheTimeout&nbsp; 300

    #&nbsp; Semaphore:
    #&nbsp; Configure the path to the mutual exclusion semaphore the
    #&nbsp; SSL engine uses internally for inter-process synchronization.
    #SSLMutex&nbsp; file:logs/ssl_mutex.log
    SSLMutex default

    #&nbsp; Pseudo Random Number Generator (PRNG):
    #&nbsp; Configure one or more sources to seed the PRNG of the
    #&nbsp; SSL library. The seed data should be of good random quality.
    #&nbsp; WARNING! On some platforms /dev/random blocks if not enough entropy
    #&nbsp; is available. This means you then cannot use the /dev/random device
    #&nbsp; because it would lead to very long connection times (as long as
    #&nbsp; it requires to make more entropy available). But usually those
    #&nbsp; platforms additionally provide a /dev/urandom device which doesn't
    #&nbsp; block. So, if available, use this one instead. Read the mod_ssl User
    #&nbsp; Manual for more details.
    SSLRandomSeed startup builtin
    SSLRandomSeed connect builtin
    #SSLRandomSeed startup file:/dev/random&nbsp; 512
    #SSLRandomSeed startup file:/dev/urandom 512
    #SSLRandomSeed connect file:/dev/random&nbsp; 512
    #SSLRandomSeed connect file:/dev/urandom 512

    ##
    ## SSL Virtual Host Context
    ##



    #&nbsp; General setup for the virtual host
    DocumentRoot "C:\Program Files\Apache Group\Apache2\htdocs_secure"
    ServerName localhost:443
    #ServerName www.my-domain.com:443
    ServerAdmin you@your.address
    ErrorLog logs/error.log
    TransferLog logs/access.log

    #&nbsp; SSL Engine Switch:
    #&nbsp; Enable/Disable SSL for this virtual host.
    SSLEngine on

    #&nbsp; SSL Cipher Suite:
    #&nbsp; List the ciphers that the client is permitted to negotiate.
    #&nbsp; See the mod_ssl documentation for a complete list.
    SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL

    #&nbsp; Server Certificate:
    #&nbsp; Point SSLCertificateFile at a PEM encoded certificate.&nbsp; If
    #&nbsp; the certificate is encrypted, then you will be prompted for a
    #&nbsp; pass phrase.&nbsp; Note that a kill -HUP will prompt again.&nbsp; Keep
    #&nbsp; in mind that if you have both an RSA and a DSA certificate you
    #&nbsp; can configure both in parallel (to also allow the use of DSA
    #&nbsp; ciphers, etc.)
    SSLCertificateFile conf/ssl/my-server.cert
    #SSLCertificateFile conf/ssl.crt/server-dsa.crt

    #&nbsp; Server Private Key:
    #&nbsp; If the key is not combined with the certificate, use this
    #&nbsp; directive to point at the key file.&nbsp; Keep in mind that if
    #&nbsp; you've both a RSA and a DSA private key you can configure
    #&nbsp; both in parallel (to also allow the use of DSA ciphers, etc.)
    SSLCertificateKeyFile conf/ssl/my-server.key
    #SSLCertificateKeyFile conf/ssl.key/server-dsa.key

    #&nbsp; Server Certificate Chain:
    #&nbsp; Point SSLCertificateChainFile at a file containing the
    #&nbsp; concatenation of PEM encoded CA certificates which form the
    #&nbsp; certificate chain for the server certificate. Alternatively
    #&nbsp; the referenced file can be the same as SSLCertificateFile
    #&nbsp; when the CA certificates are directly appended to the server
    #&nbsp; certificate for convinience.
    #SSLCertificateChainFile conf/ssl.crt/ca.crt

    #&nbsp; Certificate Authority (CA):
    #&nbsp; Set the CA certificate verification path where to find CA
    #&nbsp; certificates for client authentication or alternatively one
    #&nbsp; huge file containing all of them (file must be PEM encoded)
    #&nbsp; Note: Inside SSLCACertificatePath you need hash symlinks
    #&nbsp; &nbsp; &nbsp; &nbsp; to point to the certificate files. Use the provided
    #&nbsp; &nbsp; &nbsp; &nbsp; Makefile to update the hash symlinks after changes.
    #SSLCACertificatePath conf/ssl.crt
    #SSLCACertificateFile conf/ssl.crt/ca-bundle.crt

    #&nbsp; Certificate Revocation Lists (CRL):
    #&nbsp; Set the CA revocation path where to find CA CRLs for client
    #&nbsp; authentication or alternatively one huge file containing all
    #&nbsp; of them (file must be PEM encoded)
    #&nbsp; Note: Inside SSLCARevocationPath you need hash symlinks
    #&nbsp; &nbsp; &nbsp; &nbsp; to point to the certificate files. Use the provided
    #&nbsp; &nbsp; &nbsp; &nbsp; Makefile to update the hash symlinks after changes.
    #SSLCARevocationPath conf/ssl.crl
    #SSLCARevocationFile conf/ssl.crl/ca-bundle.crl

    #&nbsp; Client Authentication (Type):
    #&nbsp; Client certificate verification type and depth.&nbsp; Types are
    #&nbsp; none, optional, require and optional_no_ca.&nbsp; Depth is a
    #&nbsp; number which specifies how deeply to verify the certificate
    #&nbsp; issuer chain before deciding the certificate is not valid.
    #SSLVerifyClient require
    #SSLVerifyDepth&nbsp; 10

    #&nbsp; Access Control:
    #&nbsp; With SSLRequire you can do per-directory access control based
    #&nbsp; on arbitrary complex boolean expressions containing server
    #&nbsp; variable checks and other lookup directives.&nbsp; The syntax is a
    #&nbsp; mixture between C and Perl.&nbsp; See the mod_ssl documentation
    #&nbsp; for more details.
    #
    #SSLRequire (&nbsp; &nbsp; %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
    #&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
    #&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
    #&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
    #&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20&nbsp; &nbsp; &nbsp; ) \
    #&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
    #


    #&nbsp; SSL Engine Options:
    #&nbsp; Set various options for the SSL engine.
    #&nbsp; o FakeBasicAuth:
    #&nbsp; &nbsp; Translate the client X.509 into a Basic Authorisation.&nbsp; This means that
    #&nbsp; &nbsp; the standard Auth/DBMAuth methods can be used for access control.&nbsp; The
    #&nbsp; &nbsp; user name is the `one line' version of the client's X.509 certificate.
    #&nbsp; &nbsp; Note that no password is obtained from the user. Every entry in the user
    #&nbsp; &nbsp; file needs this password: `xxj31ZMTZzkVA'.
    #&nbsp; o ExportCertData:
    #&nbsp; &nbsp; This exports two additional environment variables: SSL_CLIENT_CERT and
    #&nbsp; &nbsp; SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
    #&nbsp; &nbsp; server (always existing) and the client (only existing when client
    #&nbsp; &nbsp; authentication is used). This can be used to import the certificates
    #&nbsp; &nbsp; into CGI scripts.
    #&nbsp; o StdEnvVars:
    #&nbsp; &nbsp; This exports the standard SSL/TLS related `SSL_*' environment variables.
    #&nbsp; &nbsp; Per default this exportation is switched off for performance reasons,
    #&nbsp; &nbsp; because the extraction step is an expensive operation and is usually
    #&nbsp; &nbsp; useless for serving static content. So one usually enables the
    #&nbsp; &nbsp; exportation for CGI and SSI requests only.
    #&nbsp; o CompatEnvVars:
    #&nbsp; &nbsp; This exports obsolete environment variables for backward compatibility
    #&nbsp; &nbsp; to Apache-SSL 1.x, mod_ssl 2.0.x, Sioux 1.0 and Stronghold 2.x. Use this
    #&nbsp; &nbsp; to provide compatibility to existing CGI scripts.
    #&nbsp; o StrictRequire:
    #&nbsp; &nbsp; This denies access when "SSLRequireSSL" or "SSLRequire" applied even
    #&nbsp; &nbsp; under a "Satisfy any" situation, i.e. when it applies access is denied
    #&nbsp; &nbsp; and no other module can change it.
    #&nbsp; o OptRenegotiate:
    #&nbsp; &nbsp; This enables optimized SSL connection renegotiation handling when SSL
    #&nbsp; &nbsp; directives are used in per-directory context.
    #SSLOptions +FakeBasicAuth +ExportCertData +CompatEnvVars +StrictRequire

    &nbsp; &nbsp; SSLOptions +StdEnvVars


    &nbsp; &nbsp; SSLOptions +StdEnvVars


    #&nbsp; SSL Protocol Adjustments:
    #&nbsp; The safe and default but still SSL/TLS standard compliant shutdown
    #&nbsp; approach is that mod_ssl sends the close notify alert but doesn't wait for
    #&nbsp; the close notify alert from client. When you need a different shutdown
    #&nbsp; approach you can use one of the following variables:
    #&nbsp; o ssl-unclean-shutdown:
    #&nbsp; &nbsp; This forces an unclean shutdown when the connection is closed, i.e. no
    #&nbsp; &nbsp; SSL close notify alert is send or allowed to received.&nbsp; This violates
    #&nbsp; &nbsp; the SSL/TLS standard but is needed for some brain-dead browsers. Use
    #&nbsp; &nbsp; this when you receive I/O errors because of the standard approach where
    #&nbsp; &nbsp; mod_ssl sends the close notify alert.
    #&nbsp; o ssl-accurate-shutdown:
    #&nbsp; &nbsp; This forces an accurate shutdown when the connection is closed, i.e. a
    #&nbsp; &nbsp; SSL close notify alert is send and mod_ssl waits for the close notify
    #&nbsp; &nbsp; alert of the client. This is 100% SSL/TLS standard compliant, but in
    #&nbsp; &nbsp; practice often causes hanging connections with brain-dead browsers. Use
    #&nbsp; &nbsp; this only for browsers where you know that their SSL implementation
    #&nbsp; &nbsp; works correctly.
    #&nbsp; Notice: Most problems of broken clients are also related to the HTTP
    #&nbsp; keep-alive facility, so you usually additionally want to disable
    #&nbsp; keep-alive for those clients, too. Use variable "nokeepalive" for this.
    #&nbsp; Similarly, one has to force some clients to use HTTP/1.0 to workaround
    #&nbsp; their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
    #&nbsp; "force-response-1.0" for this.
    SetEnvIf User-Agent ".*MSIE.*" \
    &nbsp; &nbsp; &nbsp; &nbsp; nokeepalive ssl-unclean-shutdown \
    &nbsp; &nbsp; &nbsp; &nbsp; downgrade-1.0 force-response-1.0

    #&nbsp; Per-Server Logging:
    #&nbsp; The home of a custom SSL log file. Use this when you want a
    #&nbsp; compact non-error SSL logfile on a virtual host basis.
    CustomLog logs/ssl_request_log \
    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"

    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;

    #




    HTTPD.CONF
    #
    # Based upon the NCSA server configuration files originally by Rob McCool.
    #
    # This is the main Apache server configuration file.&nbsp; It contains the
    # configuration directives that give the server its instructions.
    # See for detailed information about
    # the directives.
    #
    # Do NOT simply read the instructions in here without understanding
    # what they do.&nbsp; They're here only as hints or reminders.&nbsp; If you are unsure
    # consult the online docs. You have been warned.&nbsp;
    #
    # The configuration directives are grouped into three basic sections:
    #&nbsp; 1. Directives that control the operation of the Apache server process as a
    #&nbsp; &nbsp; whole (the 'global environment').
    #&nbsp; 2. Directives that define the parameters of the 'main' or 'default' server,
    #&nbsp; &nbsp; which responds to requests that aren't handled by a virtual host.
    #&nbsp; &nbsp; These directives also provide default values for the settings
    #&nbsp; &nbsp; of all virtual hosts.
    #&nbsp; 3. Settings for virtual hosts, which allow Web requests to be sent to
    #&nbsp; &nbsp; different IP addresses or hostnames and have them handled by the
    #&nbsp; &nbsp; 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.&nbsp; If the filenames do *not* begin
    # with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
    # with ServerRoot set to "C:/Program Files/Apache Group/Apache2" will be interpreted by the
    # server as "C:/Program Files/Apache Group/Apache2/logs/foo.log".
    #
    # NOTE: Where filenames are specified, you must use forward slashes
    # instead of backslashes (e.g., "c:/apache" instead of "c:\apache").
    # If a drive letter is omitted, the drive on which Apache.exe is located
    # will be used by default.&nbsp; It is recommended that you always supply
    # an explicit drive letter in absolute paths, however, to avoid
    # confusion.
    #

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

    #
    # ServerRoot: The top of the directory tree under which the server's
    # configuration, error, and log files are kept.
    #
    # NOTE!&nbsp; If you intend to place this on an NFS (or otherwise network)
    # mounted filesystem then please read the LockFile documentation (available
    # at );
    # you will save yourself a lot of trouble.
    #
    # Do NOT add a slash at the end of the directory path.
    #
    ServerRoot "C:/Program Files/Apache Group/Apache2"

    #
    # ScoreBoardFile: File used to store internal server process information.
    # If unspecified (the default), the scoreboard will be stored in an
    # anonymous shared memory segment, and will be unavailable to third-party
    # applications.
    # If specified, ensure that no two invocations of Apache share the same
    # scoreboard file. The scoreboard file MUST BE STORED ON A LOCAL DISK.
    #
    #ScoreBoardFile logs/apache_runtime_status

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

    #
    # 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 (MPM specific)
    ##

    # WinNT MPM
    # ThreadsPerChild: constant number of worker threads in the server process
    # MaxRequestsPerChild: maximum&nbsp; number of requests a server process serves

    ThreadsPerChild 250
    MaxRequestsPerChild&nbsp; 0


    #
    # Listen: Allows you to bind Apache to specific IP addresses and/or
    # ports, instead of the default. See also the
    # directive.
    #
    # Change this to Listen on specific IP addresses as shown below to
    # prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
    #
    #Listen 12.34.56.78:80
    Listen 80

    #
    # 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.
    # Statically compiled modules (those listed by `httpd -l') do not need
    # to be loaded here.
    #
    # Example:
    # LoadModule foo_module modules/mod_foo.so
    #
    LoadModule access_module modules/mod_access.so
    LoadModule actions_module modules/mod_actions.so
    LoadModule alias_module modules/mod_alias.so
    LoadModule asis_module modules/mod_asis.so
    LoadModule auth_module modules/mod_auth.so
    #LoadModule auth_anon_module modules/mod_auth_anon.so
    #LoadModule auth_dbm_module modules/mod_auth_dbm.so
    #LoadModule auth_digest_module modules/mod_auth_digest.so
    LoadModule autoindex_module modules/mod_autoindex.so
    #LoadModule cern_meta_module modules/mod_cern_meta.so
    LoadModule cgi_module modules/mod_cgi.so
    #LoadModule dav_module modules/mod_dav.so
    #LoadModule dav_fs_module modules/mod_dav_fs.so
    LoadModule dir_module modules/mod_dir.so
    LoadModule env_module modules/mod_env.so
    #LoadModule expires_module modules/mod_expires.so
    #LoadModule file_cache_module modules/mod_file_cache.so
    #LoadModule headers_module modules/mod_headers.so
    LoadModule imap_module modules/mod_imap.so
    LoadModule include_module modules/mod_include.so
    #LoadModule info_module modules/mod_info.so
    LoadModule isapi_module modules/mod_isapi.so
    LoadModule log_config_module modules/mod_log_config.so
    LoadModule mime_module modules/mod_mime.so
    #LoadModule mime_magic_module modules/mod_mime_magic.so
    #LoadModule proxy_module modules/mod_proxy.so
    #LoadModule proxy_connect_module modules/mod_proxy_connect.so
    #LoadModule proxy_http_module modules/mod_proxy_http.so
    #LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
    LoadModule negotiation_module modules/mod_negotiation.so
    #LoadModule rewrite_module modules/mod_rewrite.so
    LoadModule setenvif_module modules/mod_setenvif.so
    #LoadModule speling_module modules/mod_speling.so
    #LoadModule status_module modules/mod_status.so
    #LoadModule unique_id_module modules/mod_unique_id.so
    LoadModule userdir_module modules/mod_userdir.so
    #LoadModule usertrack_module modules/mod_usertrack.so
    #LoadModule vhost_alias_module modules/mod_vhost_alias.so
    LoadModule ssl_module modules/mod_ssl.so

    #
    # 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
    # definition.&nbsp; These values also provide defaults for
    # any containers you may define later in the file.
    #
    # All of these directives may appear inside containers,
    # in which case these default settings will be overridden for the
    # virtual host being defined.
    #

    #
    # ServerAdmin: Your address, where problems with the server should be
    # e-mailed.&nbsp; This address appears on some server-generated pages, such
    # as error documents.&nbsp; e.g. admin@your-domain.com
    #
    ServerAdmin test@test.com

    #
    # ServerName gives the name and port that the server uses to identify itself.
    # This can often be determined automatically, but we recommend you specify
    # it explicitly to prevent problems during startup.
    #
    # If this is not set to valid DNS name for your host, server-generated
    # redirections will not work.&nbsp; See also the UseCanonicalName directive.
    #
    # If your host doesn't have a registered DNS name, enter its IP address here.
    # You will have to access it by its address anyway, and this will make
    # redirections work in a sensible way.
    #
    ServerName localhost:80

    #
    # UseCanonicalName: Determines how Apache constructs self-referencing
    # URLs and the SERVER_NAME and SERVER_PORT variables.
    # When set "Off", Apache will use the Hostname and Port supplied
    # by the client.&nbsp; When set "On", Apache will use the value of the
    # ServerName directive.
    #
    UseCanonicalName Off

    #
    # 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 "C:/Program Files/Apache Group/Apache2/htdocs"

    #
    # 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
    # features.&nbsp;
    #

    &nbsp; &nbsp; Options FollowSymLinks
    &nbsp; &nbsp; 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.
    #


    #
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #&nbsp; Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    #
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    #
    # The Options directive is both complicated and important.&nbsp; Please see
    # http://httpd.apache.org/docs/2.0/mod/core.html#options
    # for more information.
    #
    &nbsp; &nbsp; Options Indexes FollowSymLinks

    #
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #&nbsp; Options FileInfo AuthConfig Limit
    #
    &nbsp; &nbsp; AllowOverride None

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



    #
    # UserDir: The name of the directory that is appended onto a user's home
    # directory if a ~user request is received.&nbsp; Be especially careful to use
    # proper, forward slashes here.&nbsp; On Windows NT, "Personal/My Website"
    # is a more appropriate choice.
    #
    UserDir "My Documents/My Website"

    #
    # Control access to UserDir directories.&nbsp; The following is an example
    # for a site where these directories are restricted to read-only.
    #
    # You must correct the path for the root to match your system's configured
    # user directory location, e.g. "C:/WinNT/profiles/*/My Documents/My Website"
    # or whichever, as appropriate.
    #
    #
    #&nbsp; &nbsp; AllowOverride FileInfo AuthConfig Limit
    #&nbsp; &nbsp; Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
    #&nbsp; &nbsp;
    #&nbsp; &nbsp; &nbsp; &nbsp; Order allow,deny
    #&nbsp; &nbsp; &nbsp; &nbsp; Allow from all
    #&nbsp; &nbsp;

    #&nbsp; &nbsp;
    #&nbsp; &nbsp; &nbsp; &nbsp; Order deny,allow
    #&nbsp; &nbsp; &nbsp; &nbsp; Deny from all
    #&nbsp; &nbsp;

    #


    #
    # DirectoryIndex: sets the file that Apache will serve if a directory
    # is requested.
    #
    # The index.html.var file (a type-map) is used to deliver content-
    # negotiated documents.&nbsp; The MultiViews Option can be used for the
    # same purpose, but it is much slower.
    #
    DirectoryIndex index.html index.html.var

    #
    # AccessFileName: The name of the file to look for in each directory
    # for additional configuration directives.&nbsp; See also the AllowOverride
    # directive.
    #
    AccessFileName .htaccess

    #
    # The following lines prevent .htaccess and .htpasswd files from being
    # viewed by Web clients.
    #

    &nbsp; &nbsp; Order allow,deny
    &nbsp; &nbsp; Deny from all


    #
    # TypesConfig describes where the mime.types file (or equivalent) is
    # to be found.
    #
    TypesConfig 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.&nbsp; 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.&nbsp; The MIMEMagicFile
    # directive tells the module where the hint definitions are located.
    #

    &nbsp; &nbsp; MIMEMagicFile conf/magic


    #
    # HostnameLookups: Log the names of clients or just their IP addresses
    # e.g., www.apache.org (on) or 204.62.129.132 (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

    #
    # EnableMMAP: Control whether memory-mapping is used to deliver
    # files (assuming that the underlying OS supports it).
    # The default is on; turn this off if you serve from NFS-mounted
    # filesystems.&nbsp; On some systems, turning it off (regardless of
    # filesystem) can improve performance; for details, please see
    # http://httpd.apache.org/docs/2.0/mod/core.html#enablemmap
    #
    #EnableMMAP off

    #
    # EnableSendfile: Control whether the sendfile kernel support is
    # used&nbsp; to deliver files (assuming that the OS supports it).
    # The default is on; turn this off if you serve from NFS-mounted
    # filesystems.&nbsp; Please see
    # http://httpd.apache.org/docs/2.0/mod/core.html#enablesendfile
    #
    #EnableSendfile off

    #
    # ErrorLog: The location of the error log file.
    # If you do not specify an ErrorLog directive within a
    # container, error messages relating to that virtual host will be
    # logged here.&nbsp; If you *do* define an error logfile for a
    # container, that host's errors will be logged there and not here.
    #
    ErrorLog 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
    LogLevel debug

    #
    # 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

    # You need to enable mod_logio.c to use %I and %O
    #LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio

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

    #
    # If you would like to have agent and referer logfiles, uncomment the
    # following directives.
    #
    #CustomLog logs/referer.log referer
    #CustomLog 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 logs/access.log combined

    #
    # ServerTokens
    # This directive configures what you return as the Server HTTP response
    # Header. The default is 'Full' which sends information about the OS-Type
    # and compiled in modules.
    # Set to one of:&nbsp; Full | OS | Minor | Minimal | Major | Prod
    # where Full conveys the most information, and Prod the least.
    #
    ServerTokens Full

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

    #
    # Aliases: Add here as many aliases as you need (with no limit). The format is
    # Alias fakename realname
    #
    # Note that if you include a trailing / on fakename then the server will
    # require it to be present in the URL.&nbsp; So "/icons" isn't aliased in this
    # example, only "/icons/".&nbsp; 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.
    #
    # We include the /icons/ alias for FancyIndexed directory listings.&nbsp; If you
    # do not use FancyIndexing, you may comment this out.
    #
    Alias /icons/ "C:/Program Files/Apache Group/Apache2/icons/"


    &nbsp; &nbsp; Options Indexes MultiViews
    &nbsp; &nbsp; AllowOverride None
    &nbsp; &nbsp; Order allow,deny
    &nbsp; &nbsp; Allow from all


    #
    # This should be changed to the ServerRoot/manual/.&nbsp; The alias provides
    # the manual, even if you choose to move your DocumentRoot.&nbsp; You may comment
    # this out if you do not care for the documentation.
    #
    AliasMatch ^/manual(?:/(?:de|en|es|fr|ja|ko|ru))?(/.*)?$ "C:/Program Files/Apache Group/Apache2/manual$1"


    &nbsp; &nbsp; Options Indexes
    &nbsp; &nbsp; AllowOverride None
    &nbsp; &nbsp; Order allow,deny
    &nbsp; &nbsp; Allow from all

    &nbsp; &nbsp;
    &nbsp; &nbsp; &nbsp; &nbsp; SetHandler type-map
    &nbsp; &nbsp;


    &nbsp; &nbsp; SetEnvIf Request_URI ^/manual/(de|en|es|fr|ja|ko|ru)/ prefer-language=$1
    &nbsp; &nbsp; RedirectMatch 301 ^/manual(?:/(de|en|es|fr|ja|ko|ru)){2,}(/.*)?$ /manual/$1$2


    #
    # 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/ "C:/Program Files/Apache Group/Apache2/cgi-bin/"

    #
    # "C:/Program Files/Apache Group/Apache2/cgi-bin" should be changed to whatever your ScriptAliased
    # CGI directory exists, if you have that configured.
    #

    &nbsp; &nbsp; AllowOverride None
    &nbsp; &nbsp; Options None
    &nbsp; &nbsp; Order allow,deny
    &nbsp; &nbsp; Allow from all


    #
    # 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.
    # Example:
    # Redirect permanent /foo http://www.example.com/bar

    #
    # Directives controlling the display of server-generated directory listings.
    #

    #
    # IndexOptions: Controls the appearance of server-generated directory
    # listings.
    #
    IndexOptions FancyIndexing VersionSort

    #
    # AddIcon* directives tell the server which icon to show for different
    # files or filename extensions.&nbsp; 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.&nbsp; 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.
    ReadmeName README.html
    HeaderName HEADER.html

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

    #
    # DefaultLanguage and 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 the user can understand.
    #
    # Specify a default language. This means that all data
    # going out without a specific language tag (see below) will
    # be marked with this one. You probably do NOT want to set
    # this unless you are sure it is correct for all cases.
    #
    # * It is generally better to not mark a page as
    # * being a certain language than marking it with the wrong
    # * language!
    #
    # DefaultLanguage nl
    #
    # 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 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. There is 'work in progress' to fix this and get
    # the reference data for rfc1766 cleaned up.
    #
    # Catalan (ca) - Croatian (hr) - Czech (cs) - Danish (da) - Dutch (nl)
    # English (en) - Esperanto (eo) - Estonian (et) - French (fr) - German (de)
    # Greek-Modern (el) - Hebrew (he) - Italian (it) - Japanese (ja)
    # Korean (ko) - Luxembourgeois* (ltz) - Norwegian Nynorsk (nn)
    # Norwegian (no) - Polish (pl) - Portugese (pt)
    # Brazilian Portuguese (pt-BR) - Russian (ru) - Swedish (sv)
    # Simplified Chinese (zh-CN) - Spanish (es) - Traditional Chinese (zh-TW)
    #
    AddLanguage ca .ca
    AddLanguage cs .cz .cs
    AddLanguage da .dk
    AddLanguage de .de
    AddLanguage el .el
    AddLanguage en .en
    AddLanguage eo .eo
    AddLanguage es .es
    AddLanguage et .et
    AddLanguage fr .fr
    AddLanguage he .he
    AddLanguage hr .hr
    AddLanguage it .it
    AddLanguage ja .ja
    AddLanguage ko .ko
    AddLanguage ltz .ltz
    AddLanguage nl .nl
    AddLanguage nn .nn
    AddLanguage no .no
    AddLanguage pl .po
    AddLanguage pt .pt
    AddLanguage pt-BR .pt-br
    AddLanguage ru .ru
    AddLanguage sv .sv
    AddLanguage zh-CN .zh-cn
    AddLanguage zh-TW .zh-tw

    #
    # LanguagePriority allows you to give precedence to some languages
    # in case of a tie during content negotiation.
    #
    # Just list the languages in decreasing order of preference. We have
    # more or less alphabetized them here. You probably want to change this.
    #
    LanguagePriority en ca cs da de el eo es et fr he hr it ja ko ltz nl nn no pl pt pt-BR ru sv zh-CN zh-TW

    #
    # ForceLanguagePriority allows you to serve a result page rather than
    # MULTIPLE CHOICES (Prefer) [in case of a tie] or NOT ACCEPTABLE (Fallback)
    # [in case no accepted languages matched the available variants]
    #
    ForceLanguagePriority Prefer Fallback

    #
    # Commonly used filename extensions to character sets. You probably
    # want to avoid clashes with the language extensions, unless you
    # are good at carefully testing your setup after each change.
    # See http://www.iana.org/assignments/character-sets for the
    # official list of charset names and their respective RFCs.
    #
    AddCharset ISO-8859-1&nbsp; .iso8859-1 .latin1
    AddCharset ISO-8859-2&nbsp; .iso8859-2 .latin2 .cen
    AddCharset ISO-8859-3&nbsp; .iso8859-3 .latin3
    AddCharset ISO-8859-4&nbsp; .iso8859-4 .latin4
    AddCharset ISO-8859-5&nbsp; .iso8859-5 .latin5 .cyr .iso-ru
    AddCharset ISO-8859-6&nbsp; .iso8859-6 .latin6 .arb
    AddCharset ISO-8859-7&nbsp; .iso8859-7 .latin7 .grk
    AddCharset ISO-8859-8&nbsp; .iso8859-8 .latin8 .heb
    AddCharset ISO-8859-9&nbsp; .iso8859-9 .latin9 .trk
    AddCharset ISO-2022-JP .iso2022-jp .jis
    AddCharset ISO-2022-KR .iso2022-kr .kis
    AddCharset ISO-2022-CN .iso2022-cn .cis
    AddCharset Big5&nbsp; &nbsp; &nbsp; &nbsp; .Big5&nbsp; &nbsp; &nbsp; .big5
    # For russian, more than one charset is used (depends on client, mostly):
    AddCharset WINDOWS-1251 .cp-1251&nbsp; .win-1251
    AddCharset CP866&nbsp; &nbsp; &nbsp; .cp866
    AddCharset KOI8-r&nbsp; &nbsp; &nbsp; .koi8-r .koi8-ru
    AddCharset KOI8-ru&nbsp; &nbsp; .koi8-uk .ua
    AddCharset ISO-10646-UCS-2 .ucs2
    AddCharset ISO-10646-UCS-4 .ucs4
    AddCharset UTF-8&nbsp; &nbsp; &nbsp; .utf8

    # The set below does not map to a specific (iso) standard
    # but works on a fairly wide range of browsers. Note that
    # capitalization actually matters (it should not, but it
    # does for some browsers).
    #
    # See http://www.iana.org/assignments/character-sets
    # for a list of sorts. But browsers support few.
    #
    AddCharset GB2312&nbsp; &nbsp; &nbsp; .gb2312 .gb
    AddCharset utf-7&nbsp; &nbsp; &nbsp; .utf7
    AddCharset utf-8&nbsp; &nbsp; &nbsp; .utf8
    AddCharset big5&nbsp; &nbsp; &nbsp; &nbsp; .big5 .b5
    AddCharset EUC-TW&nbsp; &nbsp; &nbsp; .euc-tw
    AddCharset EUC-JP&nbsp; &nbsp; &nbsp; .euc-jp
    AddCharset EUC-KR&nbsp; &nbsp; &nbsp; .euc-kr
    AddCharset shift_jis&nbsp; .sjis

    #
    # AddType allows you to add to or override the MIME configuration
    # file mime.types for specific file types.
    #
    #AddType application/x-tar .tgz
    #
    # 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
    #
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    #
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz

    #
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    #
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #
    #AddHandler cgi-script .cgi

    #
    # For files that include their own HTTP headers:
    #
    #AddHandler send-as-is asis

    #
    # For server-parsed imagemap files:
    #
    #AddHandler imap-file map

    #
    # For type maps (negotiated resources):
    # (This is enabled by default to allow the Apache "It Worked" page
    #&nbsp; to be distributed in multiple languages.)
    #
    AddHandler type-map var

    #
    # Filters allow you to process content before it is sent to the client.
    #
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml

    #
    # Action lets you define media types that will execute a script whenever
    # a matching file is called. This eliminates the need for repeated URL
    # pathnames for oft-used CGI file processors.
    # Format: Action media/type /cgi-script/location
    # Format: Action handler-name /cgi-script/location
    #

    #
    # Customizable error responses come in three flavors:
    # 1) plain text 2) local redirects 3) external redirects
    #
    # Some examples:
    #ErrorDocument 500 "The server made a boo boo."
    #ErrorDocument 404 /missing.html
    #ErrorDocument 404 "/cgi-bin/missing_handler.pl"
    #ErrorDocument 402 http://www.example.com/subscription_info.html
    #

    #
    # Putting this all together, we can internationalize error responses.
    #
    # We use Alias to redirect any /error/HTTP_.html.var response to
    # our collection of by-error message multi-language collections.&nbsp; We use
    # includes to substitute the appropriate text.
    #
    # You can modify the messages' appearance without changing any of the
    # default HTTP_.html.var files by adding the line:
    #
    #&nbsp; Alias /error/include/ "/your/include/path/"
    #
    # which allows you to create your own set of files by starting with the
    # @exp_errordir@/include/ files and copying them to /your/include/path/,
    # even on a per-VirtualHost basis.&nbsp; The default include files will display
    # your Apache version number and your ServerAdmin email address regardless
    # of the setting of ServerSignature.
    #
    # The internationalized error documents require mod_alias, mod_include
    # and mod_negotiation.&nbsp; To activate them, uncomment the following 30 lines.

    #&nbsp; &nbsp; Alias /error/ "@exp_errordir@/"
    #
    #&nbsp; &nbsp;
    #&nbsp; &nbsp; &nbsp; &nbsp; AllowOverride None
    #&nbsp; &nbsp; &nbsp; &nbsp; Options IncludesNoExec
    #&nbsp; &nbsp; &nbsp; &nbsp; AddOutputFilter Includes html
    #&nbsp; &nbsp; &nbsp; &nbsp; AddHandler type-map var
    #&nbsp; &nbsp; &nbsp; &nbsp; Order allow,deny
    #&nbsp; &nbsp; &nbsp; &nbsp; Allow from all
    #&nbsp; &nbsp; &nbsp; &nbsp; LanguagePriority en cs de es fr it ja ko nl pl pt-br ro sv tr
    #&nbsp; &nbsp; &nbsp; &nbsp; ForceLanguagePriority Prefer Fallback
    #&nbsp; &nbsp;

    #
    #&nbsp; &nbsp; ErrorDocument 400 /error/HTTP_BAD_REQUEST.html.var
    #&nbsp; &nbsp; ErrorDocument 401 /error/HTTP_UNAUTHORIZED.html.var
    #&nbsp; &nbsp; ErrorDocument 403 /error/HTTP_FORBIDDEN.html.var
    #&nbsp; &nbsp; ErrorDocument 404 /error/HTTP_NOT_FOUND.html.var
    #&nbsp; &nbsp; ErrorDocument 405 /error/HTTP_METHOD_NOT_ALLOWED.html.var
    #&nbsp; &nbsp; ErrorDocument 408 /error/HTTP_REQUEST_TIME_OUT.html.var
    #&nbsp; &nbsp; ErrorDocument 410 /error/HTTP_GONE.html.var
    #&nbsp; &nbsp; ErrorDocument 411 /error/HTTP_LENGTH_REQUIRED.html.var
    #&nbsp; &nbsp; ErrorDocument 412 /error/HTTP_PRECONDITION_FAILED.html.var
    #&nbsp; &nbsp; ErrorDocument 413 /error/HTTP_REQUEST_ENTITY_TOO_LARGE.html.var
    #&nbsp; &nbsp; ErrorDocument 414 /error/HTTP_REQUEST_URI_TOO_LARGE.html.var
    #&nbsp; &nbsp; ErrorDocument 415 /error/HTTP_UNSUPPORTED_MEDIA_TYPE.html.var
    #&nbsp; &nbsp; ErrorDocument 500 /error/HTTP_INTERNAL_SERVER_ERROR.html.var
    #&nbsp; &nbsp; ErrorDocument 501 /error/HTTP_NOT_IMPLEMENTED.html.var
    #&nbsp; &nbsp; ErrorDocument 502 /error/HTTP_BAD_GATEWAY.html.var
    #&nbsp; &nbsp; ErrorDocument 503 /error/HTTP_SERVICE_UNAVAILABLE.html.var
    #&nbsp; &nbsp; ErrorDocument 506 /error/HTTP_VARIANT_ALSO_VARIES.html.var



    #
    # The following directives modify norma

    Source: http://community.livejournal.com/apache/35519.html

  2. Email validation & quick Rails vs. PHP

    Date: 12/16/06 (PHP Community)    Keywords: php, software, database, web, apache

    Was playing with the idea of regEx'ing out the domain of an email address and then doing a gethostbyname() to verify that the email address is valid. I know in some cases this won't work, but was curious if anyone has ever tried something similar. Just trying to come up with more validation measures to protect my employeer and their customers from malicious users.


    As for Rails VS. PHP

    Rail cons
    I am on the final stage of deploying a website built in rails and it's been a fun/frustrating learning experience because I've had to build it with a legacy schema that was mangled along the same lines as scope creep (non-standard keys, non-uniform structure (integer keys here, varchar keys there, variables inside join tables, and a lot of orphaned tables forcing the client software to do what the database should be doing [out of query joins or excessive join tables]). For the most part there is a lot of good things about Rails but it's not an end all, be all tool like some people make it out to be. Multi-page/multi-object (ex. user data mixed w/ purchase data) forms are difficult, breaking the rails way of data validation. Debugging has some nice benefits, but is poorly documented and so far I have not found a Rails equivalent to DBG symbolic debugging.... the best appears to be a rails inline assert/breakpoint object that halts the entire system to allow you a glimpse of the system state at that moment but not the ability to step in/out/over.
    Lastly there is no mod_perl or mod_php like Apache component so getting Rails on a current server implementation is somewhere between entertaining to unbelievably frustrating. Further more, though rails has a couple different natively supporting webservers (light, webbrick, mongrel) they aren't as well tested or as versatile as Apache. And lastly there is little to no documentation or guidelines, so if you got to do something out of the ordinary, life gets interesting.

    Rails pro's
    On the plus side, Rails is rich in features, its easier to write C binary packages then PHP, the ActiveRecord & ActiveMailer packages are extremely versatile and thanks to standard Obj. Oriented mantra's, base/parent methods can be supplemented or completely overridden. Otherwise it's a great rapid development platform and practically promotes itself to being used in series with another scripting language if Apache 2.0's mod_proxy or similar httpd proxy service is used. `httdoc/{rails sub-dir/ &| php sub-dir/ & /static content dir}` Prototype and Scriptalicious (spelling) being embedded and wrapped by Rails helpers make Ajax/Web 2.0 stuff a breeze as well. So if you got a simple project on queue and the time to burn stumbling through Rails, I'd recommended checking it out to see if it can compliment and augment your portfolio. Just be prepared to earn your paycheck for the first couple projects. So for speed and minor enhancements to static content, PHP dominates while for complicated, Ajax heavy applications, Rails feels like a good choice.

    Source: http://community.livejournal.com/php/522413.html

  3. Apache questions

    Date: 12/17/06 (PHP Community)    Keywords: php, hosting, apache

    I have just changed hosting providers and am having a minor problem with files matching before my mod_rewrite rules get to rewrite.

    www.mydomain.com/foobar/stuff

    is matching and executing foobar.php and I don't want it to.

    I've tried changing DefaultType to text/plain so it wouldn't execute as php.
    I've tried turning off ModSpeling in case that had an effect.

    Other info: I'm using apache 2.x and php 5.2 as a fast cgi

    * * * *

    Another question I have is what type of encoding do I need to set to get degree (°) symbols and copyright (©) to display properly. At this new host they display as '?'.

    Source: http://community.livejournal.com/php/522671.html

  4. UK webhosting recs / DreamHost

    Date: 01/16/07 (WebDesign)    Keywords: php, mysql, database, sql, web, linux, hosting, apache

    1) Can anyone recommend any reliable and not too expensive UK based webhosting companies?
    (only hosting, no domain name registration needed)


    Necessary features:
    - Linux/Apache server
    - at least 150MB webspace
    - bandwith/traffic on a normal scale, the more the better *g*
    - PHP (version 4 okay, 5 better)
    - at least one MySQL database
    - FTP access and several email accounts should be a given

    A plus, but not really neccessary:
    - .htaccess
    - cgi/perl
    - shell access

    2) DreamHost as a webhost for a small business website?
    I do have a DreamHost account, mostly for dabbling around and trying out stuff, and love all their features (and low prices). But although I've never had any problems so far, hearing every now and then about down times or bad customer service makes me a bit reluctant to recommend them to a client for hosting their small business website. Opinions, anyone?

    Thanks! :-)

    Source: http://community.livejournal.com/webdesign/1208737.html

  5. UK webhosting recs ?

    Date: 01/16/07 (PHP Community)    Keywords: php, mysql, database, sql, web, linux, hosting, apache

    Can anyone recommend any reliable and not too expensive UK based webhosting companies?
    (only hosting, no domain name registration needed)

    Necessary features:
    - Linux/Apache server
    - at least 150MB webspace
    - bandwith/traffic on a normal scale, the more the better *g*
    - PHP (version 4 okay, 5 better)
    - at least one MySQL database
    - FTP access and several email accounts should be a given

    A plus, but not really neccessary:
    - .htaccess
    - cgi/perl
    - shell access

    ETA: Is DreamHost a recommendable webhost for a small business website?
    I do have a DreamHost account, mostly for dabbling around and trying out stuff, and love all their features (and low prices). But although I've never had any problems so far, hearing every now and then about down times or bad customer service makes me a bit reluctant to recommend them to a client for hosting their small business website. Opinions, anyone?

    Thanks! :-)

    Source: http://community.livejournal.com/php/530162.html

  6. UK webhosting recs / DreamHost

    Date: 01/16/07 (Web Development)    Keywords: php, mysql, database, sql, web, linux, hosting, apache

    Can anyone recommend any reliable and not too expensive UK based webhosting companies?
    (only hosting, no domain name registration needed)

    Necessary features:
    - Linux/Apache server
    - at least 150MB webspace
    - bandwith/traffic on a normal scale, the more the better *g*
    - PHP (version 4 okay, 5 better)
    - at least one MySQL database
    - FTP access and several email accounts should be a given

    A plus, but not really neccessary:
    - .htaccess
    - cgi/perl
    - shell access

    Addendum:I just saw that in this comm's user info DreamHost is recommended as a webhost.
    I do have a DreamHost account, mostly for dabbling around and trying out stuff, and love all their features (and low prices). But although I've never had any problems so far, hearing every now and then about down times or bad customer service makes me a bit reluctant to recommend them to a client for hosting their small business website.
    Opinions, anyone?

    Thanks! :-)

    Source: http://community.livejournal.com/webdev/383671.html

  7. Web Development/Design in Linux?

    Date: 02/11/07 (WebDesign)    Keywords: php, mysql, sql, web, linux, apache

    I hate to be a bit obtuse. However, I wanted to gather people's thoughts on using Linux as a web development/design platform.

    Are there any users out there that have used Linux and/or Windows in this capacity?

    If so, what web dev/design tools for Linux do you find helpful and/or comparable to Windows-based applications (outside of GIMP, Apache, MySQL, LDAP and PHP-Eclipse, of course)?

    Finally, if your user requirements for a website gave you the choice of either Mono or PHP, which would you pick and why?

    Thanks in advance!

    *cross-posted to '[info]'linux*

    Source: http://community.livejournal.com/webdesign/1220790.html

  8. Job Posting: Lead PHP developer position

    Date: 02/17/07 (PHP Community)    Keywords: php, mysql, browser, css, html, database, sql, web, linux, apache

    Schedge, an Austin based company, is reinventing scheduling.

    We are looking for an experienced Lead PHP developer.

    Have you developed enterprise scale PHP applications?
    Have you worked with technologies like AJAX and MVC?

    Then this might be the position for you!

    You'll be responsible for leading the development efforts of the core application. The position is contract-to-hire with the option of equity in the company.

    Key Areas of Responsibility:
    * PHP Application and database development
    * Work with Designers and other Developers to build complex user interfaces and data interactions
    * Write/Update functional specs

    Required Experience:
    * Enterprise scale PHP experience
    * MVC (Model-view-controller) design experience
    * Basic DOM Scripting experience
    * Basic (X)HTML & CSS experience
    * MySQL
    * Multi-browser development
    * Apache Webserver

    Preferred additional experience:
    * Experience with the CakePHP (or similar) PHP framework
    * Flash or Action Scripting experience
    * MySQL clustering
    * Code development for Linux servers

    You'll be a good fit if:
    * You “get the Web”, and understand it’s full potential.
    * Work efficiently and get it right, not just "good enough"
    * Can set and execute priorities individually and in a group
    * Effectively communicate to people of varying levels of technical expertise

    Please note: Telecommuting is possible for this position but the ideal candidate will be located in Austin, TX and available for weekly meetings.

    If you feel you are a good fit for this position please send your resume and rate per hour to jobs@schedge.com

    [Cross-Posted to several list] My apologies if you see it multiple times.

    Source: http://community.livejournal.com/php/542006.html

  9. Job Posting: Lead PHP developer position

    Date: 02/17/07 (Web Development)    Keywords: php, mysql, browser, css, html, database, sql, web, linux, apache

    Schedge, an Austin based company, is reinventing scheduling.

    We are looking for an experienced Lead PHP developer.

    Have you developed enterprise scale PHP applications?
    Have you worked with technologies like AJAX and MVC?

    Then this might be the position for you!

    You'll be responsible for leading the development efforts of the core application. The position is contract-to-hire with the option of equity in the company.

    Key Areas of Responsibility:
    * PHP Application and database development
    * Work with Designers and other Developers to build complex user interfaces and data interactions
    * Write/Update functional specs

    Required Experience:
    * Enterprise scale PHP experience
    * MVC (Model-view-controller) design experience
    * Basic DOM Scripting experience
    * Basic (X)HTML & CSS experience
    * MySQL
    * Multi-browser development
    * Apache Webserver

    Preferred additional experience:
    * Experience with the CakePHP (or similar) PHP framework
    * Flash or Action Scripting experience
    * MySQL clustering
    * Code development for Linux servers

    You'll be a good fit if:
    * You “get the Web”, and understand it’s full potential.
    * Work efficiently and get it right, not just "good enough"
    * Can set and execute priorities individually and in a group
    * Effectively communicate to people of varying levels of technical expertise

    Please note: Telecommuting is possible for this position but the ideal candidate will be located in Austin, TX and available for weekly meetings.

    If you feel you are a good fit for this position please send your resume and rate per hour to jobs@schedge.com

    [Cross-Posted to several list] My apologies if you see it multiple times.

    Source: http://community.livejournal.com/webdev/387663.html

  10. Job Posting: Lead PHP developer position

    Date: 02/17/07 (PHP Development)    Keywords: php, mysql, browser, css, html, database, sql, web, linux, apache

    Schedge, an Austin based company, is reinventing scheduling.

    We are looking for an experienced Lead PHP developer.

    Have you developed enterprise scale PHP applications?
    Have you worked with technologies like AJAX and MVC?

    Then this might be the position for you!

    You'll be responsible for leading the development efforts of the core application. The position is contract-to-hire with the option of equity in the company.

    Key Areas of Responsibility:
    * PHP Application and database development
    * Work with Designers and other Developers to build complex user interfaces and data interactions
    * Write/Update functional specs

    Required Experience:
    * Enterprise scale PHP experience
    * MVC (Model-view-controller) design experience
    * Basic DOM Scripting experience
    * Basic (X)HTML & CSS experience
    * MySQL
    * Multi-browser development
    * Apache Webserver

    Preferred additional experience:
    * Experience with the CakePHP (or similar) PHP framework
    * Flash or Action Scripting experience
    * MySQL clustering
    * Code development for Linux servers

    You'll be a good fit if:
    * You “get the Web”, and understand it’s full potential.
    * Work efficiently and get it right, not just "good enough"
    * Can set and execute priorities individually and in a group
    * Effectively communicate to people of varying levels of technical expertise

    Please note: Telecommuting is possible for this position but the ideal candidate will be located in Austin, TX and available for weekly meetings.

    If you feel you are a good fit for this position please send your resume and rate per hour to jobs@schedge.com

    [Cross-Posted to several list] My apologies if you see it multiple times.

    Source: http://community.livejournal.com/php_dev/75751.html

  11. PHP webmail / Dreamhost

    Date: 02/18/07 (PHP Community)    Keywords: php, web, hosting, apache

    I have Dreamhost for my mail and hosting package, but I abhore Squirrelmail. So I'm researching other PHP webmail systems that I can install without too much trouble, because I'm not very familiar with installing things from the source.

    I loved Horde when I had them on my previous host, so I'm trying to install that. I haven't quite gotten to the install part yet - I'm on the Prerequisites part! I've been starting to install PHP5 (with these and these instructions) and I'm trying to make sure I get all the extra packages downloaded and whatnot before I start with the configure script. But I'm confused at a few things.

    1. Dreamhost says they like PHP to run as CGI but the Horde instructions say to configure it with --with=apache or -apxs or -apxs2. Neither of the install steps tutorials have it listed; would something bad happen if I ran it with -apxs?

    2. The tutorials also have --without-pear in the configuring, but I think I need it for Horde. Would I need to download additional packages before installing or can I just wait and install it afterwards?

    3. The Horde instructions say I need PECL modules but I absolutely cannot get fileinfo to install. It's late and I lost the error message, but since I'm doing everything from scratch, can someone tell me what I should be setting up beforehand and seeing (or not seeing) during installation?

    Thanks all.

    Source: http://community.livejournal.com/php/542333.html

  12. Stupid Error

    Date: 03/15/07 (PHP Community)    Keywords: php, mysql, sql, apache

    Can someone point out what I am not seeing here?

    I am using WAMP (Winblows-Apache-MySQL-PHP) on a server that I am forced to work on. I uncommented the mod_rewrite line in httpd.conf.

    From php_info():

    Loaded Modules  
    
    core mod_win32 mpm_winnt http_core mod_so mod_php5 mod_actions mod_alias mod_asis 
    mod_auth_basic mod_authn_default mod_authn_file mod_authz_default mod_authz_groupfile
    mod_authz_host mod_authz_user mod_autoindex mod_cgi mod_dir mod_env mod_imagemap
    mod_include mod_isapi mod_log_config mod_mime mod_negotiation mod_rewrite mod_setenvif mod_userdir


    AllowOverride is set to All by default, which means that the server will indeed look for .htaccess files.

    To test, I set up a dummy .htaccess file, which is in the root dir:

    Options +FollowSymlinks
    RewriteEngine on
    RewriteBase /
    RewriteRule ^page/([A-Za-z-]+)$ /index.php?test=$1 [QSA,L]
    


    And the end result is a 404 error. I've tried every possible combo of rewrite syntax, rules, conditions, etc.

    Does anyone have any ideas here?? I've never tried mod_rewrite on winblows, but the OS shouldn't matter as long as I'm running Apache and not IIS.

    Source: http://community.livejournal.com/php/552343.html

  13. Tomcat caching .. or?

    Date: 03/16/07 (Web Development)    Keywords: browser, jsp, apache

    Very strange issue. I don't manage the server myself, but can request changes to its configuration.

    The server is Apache Tomcat/5.5.9. We usually just write JSP files in Dreamweaver and upload them to the server.

    Now here's the issue: Whenever we update a JSP file on the site and then go to view it in the browser, with equal probability we may see the old version of the file or the new one. If we make another change to the file, we may see any of the 3. This isn't a "local" caching issue because if I at the same time try this from another machine on another network, I get the same results.

    We have attempted to delete the "cache" folder, but this doesn't generally help.

    Any ideas?

    Source: http://community.livejournal.com/webdev/395469.html

  14. Jobs...

    Date: 04/17/07 (PHP Community)    Keywords: php, programming, mysql, software, browser, css, html, xml, technology, database, sql, java, jsp, web, linux, microsoft, apache

    Moderator, if this isn't allowed on this forum just let me know.

    I get a lot of emails daily for various web dev and programming positions available. I found a good job, but I keep my resume up. Ya never know.

    Just feel guilty constantly deleting them when I know someone may need them. Figured I'd at least post them for any coder friends that may be looking for something. I lj-cut it so it wouldn't be too obtrusive.

    If these are just found to be crap, let me know and I'll stop passing them on. But some of them at least appear to have potential. They're all fresh over the past 24 hours.

    To whoever is currently looking, hope these help! If it's ok, I'll send periodic digests of these if anyone finds them worthwhile.


    Hello,


    I came across your resume and would to speak with you in regards to 2 immediate Cold Fusion needs in the Radford, VA areas.

    Here are the details.


    We need people onsite! 40 hour work week schedules

    Location/Address: Radford, VA (Southwestern VA)

    Start Date: ASAP

    Drop Dead Start Date: ASAP

    Project End date: N/A

    # Of resources need for role: 1

    Position Title: ColdFusion Software Engineer

    BE Level/ Job classification: Consultant

    Required Skill Set (Yrs Exp):


    SKILLS: ColdFusion software developer with experience leading the development of software modules.

    EXPERIENCE:
    Proven experience analyzing system requirements, guiding overall application development and individual module development. Direct involvement in application development, maintenance and operations of an application environment involving Microsoft SQL Server back-end with Macromedia ColdFusion middleware running on Microsoft IIS webservers.

    Specific education and experience requirements include:
    1. Minimum 4-year technical degree in Computer Science, Information Technology, or related field from accredited institution
    2. Minimum 1 year general programming experience and an additional 1 year experience in web-based application development
    3. Minimum 1 year experience with design, development and maintenance of ColdFusion-based online software applications
    4. Practical experience in MS SQL Server (v7 or higher) database design, operations, and maintenance involving extensive structured query language (SQL) usage and development of complex queries and procedures
    5. Practical experience with MS SQL Server (v7 or higher) database administration
    5. Must be a US Citizen
    6. Prefer current active Department of Defense (or capable of attaining) Secret Clearance

    Preferred Skill Set

    Will also consider candidates with Java and JSP experience.



    Job#2

    Location/Address: Radford, VA (Southwestern VA)

    Background of Project:

    Start Date: ASAP

    Drop Dead Start Date: ASAP

    Project End date: N/A

    # Of resources need for role: 1

    Position Title: Web Page Designer

    BE Level/ Job classification: Sr Systems Analyst

    Required Skill Set (Yrs Exp):

    The candidates we are seeking should be self starters, interested in seeking new ways to help this customer innovate and provide state of the art web design capabilities to DoD customers.

    Technical & functional requirements:

    - 1-2 years ColdFusion development experience using Version 6.0 or 7.0 (prefer 7.0)
    - 1-2 years experience with Enterprise level database design including stored procedures and functions.
    - working knowledge of the Fusebox design methodology, using version 3.0 or higher to develop robust web applications.
    - proficient with use of Visual Mind software, version 7
    - demonstrate ability to elicit requirement definitions from customers, then convert those specifications into realistic software development projects, and further develop a schedule in MS Project for task delegation and performance tracking.
    - US Citizen

    Preferred Skill Set

    XHTML or similar browser based scripting development, web services development experience a plus.
    - Cascading Style Sheet development using CSS v2.0 or later preferred.
    - Microsoft SQL Server 2000 database design experience preferred.

    Please forward me an updated word copy of your resume and give me a call.

    Thanks!

    Ray Santos | 1-800-627-8323 x9509 | rsantos@mastech.com Mastech | 1000 Commerce Drive Pittsburgh, PA 15275 | Ph:1.888.330.5497 x 9509

    Fax: 412-291-3037


    Mastech respects your privacy. We will not share your resume or contact details with any of our clients without your consent.









    Greetings!!!!!!

    VIVA USA INC., (www.viva-it.com) is an IT consulting firm headquartered in Rolling Meadows , IL servicing clients nationwide. We specialize in IT, telecom, engineering Staffing Solutions and system integration

    Please respond with your word document résumé, hourly rate, availability, visa status and relocation details to. recruit07@viva-it.com. One of our recruiters will get back to you ASAP. Kindly find below the job description.

    POSITION : Web Designer

    LOCATION : Columbia , SC

    DURATION : 6 Months

    Job Description :
    To create a new web site to replace the old web site.

    Required Skills: Web Developer, Web Site Design, Dreamweaver

    Optional Skills: .Net, XML

    Sukanya

    Viva USA INC, Chicago IL

    Phone: 847-448-0727 Ext 207

    Fax: 847-483-1317

    www.viva-it.com

    An ISO 9001:200 & CMMi M/WBE Company






    I saw your resume on Careerbuilder and thought you may be interested in this opportunity. BMW Manufacturing is looking to hire a Web developer for some contract work in their Greer, SC plant. I’ve included the details below. If you are interested, or know someone who may be, please contact me ASAP. I look forward to hearing from you soon.

    Sincerely,

    Aaron C. Fisher
    Sr. Account Representative
    Information Technology Division
    Greytree Partners, LLC


    (704) 815-1288 Office
    (704) 973-0767 Fax
    (704) 607-8518 Cell

    aaron.fisher@greytreepartners.com
    www.greytreepartners.com

    Entry Level – Web Developer Opportunity at BMW Manufacturing in Greer , South Carolina
    Client: BMW Manufacturing
    Job Title: Web Developer / Designer
    Assignment Length: 3 to 4 Weeks
    Shift: 1st / Full time
    Responsibilities: Update / refresh current departmental web content. Evaluate simple content management alternatives.
    Start Date: 23 April 2007
    Estimated End Date: 31 May 2007
    Required Skills: HTML
    Pre-Employment: Drug screen, background check (no education required).






    I have an exciting opportunity available for a PHP developer. I know the location may not be ideal but I felt it would be worth a look.

    Location: Las Vegas, NV

    Length: Contract to Hire/Direct Hire

    Rate: Depends on experience

    Required Skill Set:

    Extensive advanced PHP experience
    Back end PHP programming experience
    Experience with PHP 5
    Experience with MySQL
    Strong understanding of advanced Object Oriented Programming principles is a must

    For further consideration, please email your resume in Word format to cwander@yorksolutions.net.

    Thank You!

    Christi Wander
    York Enterprise Solutions
    cwander@yorksolutions.net






    Good afternoon,

    I came across your resume today on Monster.com and I have a position available that your skill set seems to match quite well. We are looking for a L.A.M.P. (Linux, apache, MySql, PHP) Developer candidate for a full time permanent opening in Toledo . This position is available with a great Online Bill Payment company, headquartered in Toledo and Washington D.C. This position is looking to go permanent in the 35 – 50K range, dependent upon experience. Ultimately, we are looking for someone with at least 3-5 years experience; comfortable in a lead type of role. If you are interested in discussing this opening with me, please feel free to email or call me at your earliest convenience.

    I look forward to speaking with you soon,

    Carl

    Carl Saad
    Manager of Branch Recruiting
    T 734-462-9505
    F 734-462-6443
    csaad@otterbase.com
    www.otterbase.com






    Hello! My name is Kristie Butler and I work for Procom Services, an IT Staffing Company. I am currently seeking a Web Designer for a 6 month contract position based in Columbia, SC. This position requires the following:

    The client is lookikng to create a new web site to replace the old web
    site. They are a Windows Department and they are looking for a public and private side (logon) in Web site. This will be a temp position, possible temp to hire position.

    Required Skills:

    Web Developer
    Web Site Design
    Dreamweaver
    Organizational Skills
    Written Communication Skills
    Adobe Photoshop
    Windows XP
    .Net
    XML

    If you feel you possess these skills and you are interested in this position, please send a current word document of your resume to kristieb@procomservices.com.

    Thank you!

    Kristie Butler
    Procom Services
    1-800-678-4590
    kristieb@procomservices.com

    Source: http://community.livejournal.com/php/561562.html

  15. "You don't have permission to access.."

    Date: 04/25/07 (Apache)    Keywords: php, mysql, sql, apache

    I'm running Apache 2.2 from wamp (so I have PHP5 and MySQL 5, though I don't think it has anything to do with them) on Windows XP. Anyway.

    I can access everything fine using "localhost", and a friend told me that I could access my server by just using my computer's name. So I named my computer "nemo-serv" (all my electrical devices are named after characters from Finding Nemo, my laptop is Nemo,) and then could use nemo-serv fine, just like localhost.

    Then I changed something, and I just get a "You don't have permission to access this directory" when using nemo-serv, though localhost is still fine. I really have no idea what I changed that could have done this, but I was hoping you guys would be able to point me in the right direction.

    Thanks ^^

    Source: http://community.livejournal.com/apache/36535.html

  16. Redirecting with mod_rewrite and a map

    Date: 05/20/07 (Web Development)    Keywords: html, apache

    I'm trying to do some redirections using apache mod_rewrite with a map file, and I have it working in part, when in the case where the URL is in the map it should redirect and it currently does that, however I am trying to figure out how to make it do nothing when the URL is NOT in the map and this has not (yet) worked for me.

    Here is the basic form of the rewrite configuarions,

    RewriteMap    vhost        txt:/var/www/html/vhost.map

    RewriteCond   %{HTTP_COOKIE} !^(MY_REDIRECT)
    RewriteCond   %{HTTP_HOST}   (.*.host.org)
    RewriteRule   . ${vhost:%1} [R,CO=MY_REDIRECT:ZLIO_REDIRECT:host.org:1]
    Thank you in advance

    Source: http://community.livejournal.com/webdev/409790.html

  17. permissions problem

    Date: 05/23/07 (PHP Community)    Keywords: database, linux, apache

    Have all these pdfs on a linux server here at work. They are associated by id numbers in a database. Sometimes the pdfs are assigned a wrong number so I have a script that changes where they are stored and what number they have in the database. Everytime I try to do it though I get an error on rename (which I'm also using to move files). Says permission denied.The files are owned by the "tech" user and the user trying to rename them is "apache". But I the pdfs are set to 777 so I don't understand why it doesn't have permission. Any suggestions?

    *edit*
    Used a perl script instead. Problem solved.

    Source: http://community.livejournal.com/php/567585.html

  18. aQuantive is not a Microsoft open source play

    Date: 05/29/07 (Open Source)    Keywords: mysql, software, sql, linux, microsoft, apache

    Writer Rodney Gedda at Computerworld writes that aQuantive, the online ad agency Microsoft is buying for $6 billion, is an open source play. The reason? Many aQuantive units, including AvenueA Razorfish and Atlas, make extensive use of open source software, including mySQL, Linux, and Apache. If you use open source, are you ...

    Source: http://feeds.feedburner.com/~r/zdnet/open-source/~3/120506500/

  19. Graphical interface for MySQL?

    Date: 06/08/07 (MySQL Communtiy)    Keywords: php, mysql, sql, web, apache

    I have what is probably an easy question, but I've been Googling and don't quite know where to go.

    I write and test MySQL queries on a virtual Apache server on my PC before transferring it to the live server on a website. At the moment, I write the MySQL through a command-line interface, which makes it very difficult (almost impossible) to go back and edit the query if I need to change things or have made mistakes. It seems to take much longer to develop things than it should!

    At work, I use Teradata SQL and we have a nice graphical interface where we can type in SQL, edit it easily, save SQL to re-use and all those good things. It's much easier to develop in and also easier to copy and paste the query into other files, such as Excel or PHP.

    Can anyone recommend a good equivalent program for MySQL?

    Source: http://community.livejournal.com/mysql/114511.html

  20. Development Server on Ubuntu Desktop

    Date: 06/10/07 (Webmaster View)    Keywords: php, mysql, software, browser, html, database, sql, linux, apache

    Ubuntu

    Last month,I did a clean install of Ubuntu Feisty Fawn on my home computer removing the "dapper drake". But it is only now, I got a chance to sit down and install all necessary packages to set up my development server again.

    With Dapper Drake, I had to use alien to convert MySQL5 rpm to .deb, because there was no version 5 in the repositories. Anyway, Feisty has all newest versions of software.

    This is what I did for setting up my development server:

    For installing MySQL server I ran the command: sudo apt-get install mysql-server. Then I installed the following:

    MySQL Administrator: It is a Graphical User Interface for administrating MySQL: sudo apt-get install mysql-admin

    MySQL Query Browser is a GUI for managing databases: sudo apt-get install mysql-query-browser

    Apache: sudo apt-get install apache2

    Apache Manual: sudo apt-get install apache2-doc

    PHP: sudo apt-get install php5

    PHP module for Apache: sudo apt-get install libapache2-mod-php5

    Enabling public_html directories for users

    Well, I am the only user in my computer. But I can create and edit files without running sudo if I have a public_html directory at my home. sudo a2enmod userdir. I then restarted Apache and created a 'public_html' directory in my home. Now I can access it with http://localhost/~username/.

    Enable mod_rewrite

    1. sudo a2enmod rewrite.
    2. Edit Apache configuration: sudo gedit /etc/apache2/sites-available/default
    3. Change line 12: “AllowOverride none” to “AllowOverride all”
    4. save and close
    5. Restart Apache

    (Thanks to mod_rewrite for Apache2 in Ubuntu Feisty Fawn 7.04)

    How to restart Apache?

    sudo /etc/init.d/apache2 force-reload.

    Todo:

    1. Install IEs4Linux.
    2. Install Opera.
    3. Install Komodo Edit.
    4. Install gftp.

    Source: http://www.webmasterview.com/server_side/development_server_on_ubuntu_desktop

Previous page  ||  Next page


antivirus | apache | asp | blogging | browser | bugtracking | cms | crm | css | database | ebay | ecommerce | google | hosting | html | java | jsp | linux | microsoft | mysql | offshore | offshoring | oscommerce | php | postgresql | programming | rss | security | seo | shopping | software | spam | spyware | sql | technology | templates | tracker | virus | web | xml | yahoo | home