Find the answer to your Linux question:
Results 1 to 9 of 9
Hi people, I'm using: * Red Hat Linux 8.0 * Apache 2.0.40-11.5 * openssl 0.9.6b-33 Now I've tried setting up a ssl so I can access my stuff with https://...etc ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Jul 2003
    Location
    The Netherlands, Purmerend
    Posts
    4

    [Apache-SSL]: Invalid method in request !g!!


    Hi people,

    I'm using:


    * Red Hat Linux 8.0
    * Apache 2.0.40-11.5
    * openssl 0.9.6b-33



    Now I've tried setting up a ssl so I can access my stuff with https://...etc... Everything configured and httpd starts with no errors.

    Now when I try to access my site with https://192.168.77.2/webmail or with https://ting/webmail with Mozilla 1.4 I get this dialogbox:

    "The connection to 192.168.77.2 has terminated unexpectedly. Some data may have been transferred. [OK]"

    In IE 6.0 I get: a "The page can not be displayed" error when going to the url's mentioned above.

    In the error_log of apache I see this when trying with Mozilla:
    [Sun Jul 20 11:16:55 2003] [error] [client 192.168.77.16] Invalid method in request !g!!

    This one occurs only when I try with IE:
    [Sun Jul 20 11:25:12 2003] [error] [client 192.168.77.16] Invalid method in request !L!!

    Can anyone help me with this?

    About the config. This is the only thing I added to httpd.conf to try make ssl work:
    Listen 192.168.77.2:443
    Listen ting:443

    This is what my ssl.conf looks like (I've included it within httpd.conf):

    <VirtualHost 192.168.77.2:443>
    ServerName ting
    ServerAlias ting.innertruth.net
    DocumentRoot /var/www/html
    TransferLog /var/log/httpd/access_secure_log
    ErrorLog /var/log/httpd/error_secure_log
    SSLLog /var/log/httpd/ssl_log
    SSLLogLevel trace
    SSLEngine on
    SSLCertificateFile /usr/share/ssl/ting.crt
    SSLCertificateKeyFile /usr/share/ssl/ting.key
    SSLCACertificatePath /usr/share/ssl/certs
    SSLCARevocationPath /usr/share/ssl/certs
    SSLCipherSuite ALL:!EXP:!LOW:!ADH:+HIGH:+MEDIUM
    #
    #Allow users who possess a valid certificate to access the /extranet URI.
    #
    Alias /webmail/ /var/www/html/webmail/
    <Directory /var/www/html/webmail>
    SSLVerifyClient require
    SSLVerifyDepth 1
    </Directory>
    </VirtualHost>

    Any help on this is greatly appreciated.

    Cheers,

    Gahan

  2. #2
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    Now I'm not sure about this, but I don't think that you should have a Listen directive in your main httpd.conf for the SSL server. I think that will override the vhost. Try commenting it out.

  3. #3
    Just Joined!
    Join Date
    Jul 2003
    Location
    The Netherlands, Purmerend
    Posts
    4
    Hi Dolda2000,

    I've commented it out and from mozilla I get a dialog box saying:

    "The connection was refused when contacting 192.168.77.2 [OK]"

    I hope you have some other ideas I can try that might help me.

  4. #4
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    I don't really remember how to configure Apache 2. I replaced my Apache 2 server with Apache 1.3 to enable MySQL transfer logging.
    I _think_ that you might have to move that SSL Listen directive inside the vhost declaration block, though. Try it and see if it works. It would be logical since Listen directives should apply to whatever vhost block they appear in, and having one outside should make the normal TCP server listen there, since anything outside any vhost block applies to the default server.

  5. #5
    Linux User
    Join Date
    May 2003
    Location
    CA
    Posts
    370
    Hi

    I have installed Apache2.X and openssl and this is the config that I have:

    in httpd.conf
    Listen 94 (the port that runs ssl)
    <IfModule mod_ssl.c>
    Include conf/ssl.conf
    </IfModule>

    and in ssl.conf hash out the line that says Listen 443,
    hash out the line that says SSLCACertificatePath
    and you should be good to go.
    I did not have to modify anythg else in my config.
    Hope this helps.

  6. #6
    Just Joined!
    Join Date
    Jul 2003
    Location
    The Netherlands, Purmerend
    Posts
    4
    Hi Nikhil,

    Thanks for your reply. I've tried to make some adjustments to my httpd.conf and ssl.conf on the basis of your reply. I'm still having trouble.

    Would you be so kind to paste your httpd.conf and ssl.conf here so I can look for the solution? I would greatly appreciate this!

  7. #7
    Just Joined!
    Join Date
    Jul 2003
    Location
    The Netherlands, Purmerend
    Posts
    4
    Or maybe anyone else can post his apache 2.0 (pref. Red Hat 8.0) httpd.conf and ssl.conf file with succesfull https connection? Cause I can't make heads or tails from it. I've consulted several books now and used the examples, also tried almost every tutorial on the net. This is my last resort!

    Please help me!

  8. #8
    qaz
    qaz is offline
    Just Joined!
    Join Date
    Dec 2003
    Posts
    2
    i think a certificate should be generated also httpd.conf , if ##
    ## SSL Virtual Host Context
    ##

    <VirtualHost _default_:443>

    # General setup for the virtual host
    DocumentRoot "/home"
    ServerName was.com
    #ServerName 10.1.27.106
    ServerAdmin as@was.com
    # 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:+SSL v2:+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. A test
    # certificate can be generated with `make certificate' under
    # built time. Keep in mind that if you've both a RSA and a DSA
    # certificate you can configure both in parallel (to also allow
    # the use of DSA ciphers, etc.)
    #SSLCertificateFile /usr/local/apache/conf/ssl.crt/server.crt
    #SSLCertificateFile /usr/local/apache/conf/ssl.crt/server-dsa.crt
    SSLCertificateFile /usr/local/apache/conf/ssl.crt/22112002.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 /usr/local/apache/conf/ssl.key/server.key
    #SSLCertificateKeyFile /usr/local/apache/conf/ssl.key/server-dsa.key
    SSLCertificateKeyFile /usr/local/apache/conf/ssl.key/server12.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 /usr/local/apache/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 /usr/local/apache/conf/ssl.crt
    #SSLCACertificateFile /usr/local/apache/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 /usr/local/apache/conf/ssl.crl
    #SSLCARevocationFile /usr/local/apache/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.
    #<Location />
    #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]+$/
    #</Location>

    # 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
    <Files ~ "\.(cgi|shtml|phtml|php3?)$">
    SSLOptions +StdEnvVars
    </Files>
    <Directory "/usr/local/apache/cgi-bin">
    SSLOptions +StdEnvVars
    </Directory>

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

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

    </VirtualHost>

  9. #9
    Just Joined!
    Join Date
    May 2008
    Posts
    1
    For me the answer was here, not using a hostname (i.e. use IP#) for ssl hosts.

    SSL/TLS Strong Encryption: FAQ - Apache HTTP Server

    I know this thread is stale but I wanted to post my find somewhere because I had a hard time finding it myself.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •