wiki:TipAndDoc/network/httpd

  1. suEXEC
  2. Server Maintenance
  3. Name-based VirtualHost with SSL
  4. mod_proxy
  5. mod_rewrite
  6. ScriptAlias

  • ​http://wiki.apache.org/httpd/InternalDummyConnection

    When the Apache HTTP Server manages its child processes, it needs a way to wake up processes that are listening for new connections. To do this, it sends a simple HTTP request back to itself. This request will appear in the access_log file with the remote address set to the loop-back interface (typically 127.0.0.1 or ::1 if IPv6 is configured). If you log the User-Agent string (as in the combined log format), you will see the server signature followed by "(internal dummy connection)" on non-SSL servers. During certain periods you may see up to one such request for each httpd child process.

suEXEC

Server Maintenance

  • ex) /etc/apache2/sites-available/default 
            RewriteEngine On
        RewriteCond %{REQUEST_URI} !^/maintenance/.*
        RewriteRule ^.*$ - [R=503,L]
        ErrorDocument 503 /maintenance/

Name-based VirtualHost with SSL

  • ​名前ベースのバーチャルホストで複数ドメインにSSLを割り当てることは可能か？
    • 本質的な問題 
      HTTP プロトコルと SSL の原理を考えてみても不可能なことは明らかですね。
ネームベースのバーチャルホストは、HTTP リクエストヘッダに含まれる「Host」を参照 して
アクセスするバーチャルホストを変化させますが、
SSL 接続の場合、HTTP リクエストヘッダは暗号化されており、
参照することができません。

参照するためには、暗号を解読してやればよいわけですが、
暗号を解読するためには先に証明書の交換を行う必要がありますね。
  • ​Why is it not possible to use Name-Based Virtual Hosting to identify different SSL virtual hosts?
    • It is possible, but only if using a 2.2.12 or later web server, built with 0.9.8j or later OpenSSL. This is because it requires a feature that only the most recent revisions of the SSL specification added, called Server Name Indication (SNI).
    • The reason is that the SSL protocol is a separate layer which encapsulates the HTTP protocol. So the SSL session is a separate transaction, that takes place before the HTTP session has begun. The server receives an SSL request on IP address X and port Y (usually 443). Since the SSL request did not contain any Host: field, the server had no way to decide which SSL virtual host to use. Usually, it just used the first one it found which matched the port and IP address specified.
  • ただし、全てのVirtualHostで同じワイルドカード証明書を指定すれば可能

mod_proxy

mod_rewrite

ScriptAlias

  • Apache/2.2.22
  • /home/mitty/env.cgi 
    #!/usr/bin/perl -w
print "Content-Type: text/plain\r\n\r\n";

foreach $key (sort(keys %ENV)) {
    print "$key = $ENV{$key}\n";
}

print "--------------------\n";

use CGI;
my $cgi = CGI->new;
print "url => ", $cgi->url(), "\n";
print "url(absolute) => ", $cgi->url(-absolute => 1), "\n";
print "url(base) => ", $cgi->url(-base => 1), "\n";
Apache Conf wget ​https://lab.mitty.jp/env/ wget ​https://lab.mitty.jp/env/hoge
ScriptAlias /env /home/mitty/env.cgi
ScriptAlias /env /home/mitty/env.cgi/
ScriptAlias /env/ /home/mitty/env.cgi/		PATH_INFO = /
PATH_TRANSLATED = /path/to/docroot/index.html
QUERY_STRING =
REQUEST_METHOD = GET
REQUEST_URI = /env/
SCRIPT_FILENAME = /home/mitty/env.cgi
SCRIPT_NAME = /env
SCRIPT_URI = ​https://lab.mitty.jp/env/
SCRIPT_URL = /env/
--------------------
url => ​https://lab.mitty.jp/env
url(absolute) => /env
url(base) => ​https://lab.mitty.jp		PATH_INFO = /hoge
PATH_TRANSLATED = /path/to/docroot/hoge
QUERY_STRING =
REQUEST_METHOD = GET
REQUEST_URI = /env/hoge
SCRIPT_FILENAME = /home/mitty/env.cgi
SCRIPT_NAME = /env
SCRIPT_URI = ​https://lab.mitty.jp/env/hoge
SCRIPT_URL = /env/hoge
--------------------
url => ​https://lab.mitty.jp/env
url(absolute) => /env
url(base) => ​https://lab.mitty.jp
ScriptAlias /env/ /home/mitty/env.cgi QUERY_STRING =
REQUEST_METHOD = GET
REQUEST_URI = /env/
SCRIPT_FILENAME = /home/mitty/env.cgi
SCRIPT_NAME = /env/
SCRIPT_URI = ​https://lab.mitty.jp/env/
SCRIPT_URL = /env/
--------------------
url => ​https://lab.mitty.jp/env/
url(absolute) => /env/
url(base) => ​https://lab.mitty.jp		404 Not Found
script not found or unable to stat: /home/mitty/env.cgihoge
Last modified 12 years ago Last modified on Jun 14, 2013 12:23:25 AM