<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>jisava &#187; Apacheサーバー設定</title>
	<atom:link href="http://www.yuichi.ne.jp/jisava/category/apache%e3%82%b5%e3%83%bc%e3%83%90%e3%83%bc%e8%a8%ad%e5%ae%9a/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.yuichi.ne.jp/jisava</link>
	<description>WindowsOSベースの自宅サーバー設定</description>
	<lastBuildDate>Thu, 12 Aug 2010 07:03:48 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>ja</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>サーバーメモリ不足</title>
		<link>http://www.yuichi.ne.jp/jisava/2010/04/%e3%82%b5%e3%83%bc%e3%83%90%e3%83%bc%e3%83%a1%e3%83%a2%e3%83%aa%e4%b8%8d%e8%b6%b3/</link>
		<comments>http://www.yuichi.ne.jp/jisava/2010/04/%e3%82%b5%e3%83%bc%e3%83%90%e3%83%bc%e3%83%a1%e3%83%a2%e3%83%aa%e4%b8%8d%e8%b6%b3/#comments</comments>
		<pubDate>Fri, 02 Apr 2010 05:18:45 +0000</pubDate>
		<dc:creator>jisava</dc:creator>
				<category><![CDATA[Apacheサーバー設定]]></category>
		<category><![CDATA[サーバー]]></category>
		<category><![CDATA[メモリ]]></category>

		<guid isPermaLink="false">http://www.yuichi.ne.jp/jisava/?p=572</guid>
		<description><![CDATA[現在ボロボロのパソコンでサーバー組んでいる為、メモリ「512MB」不足で不安定です。で不安定な動作解消するべく、こんなソフト入れてみました。超軽量メモリ管理ソフト「びーめむLT」 あのBeMemを超軽量化!
開発はC++ [...]]]></description>
			<content:encoded><![CDATA[<p>現在ボロボロのパソコンでサーバー組んでいる為、メモリ「512MB」不足で不安定です。で不安定な動作解消するべく、こんなソフト入れてみました。超軽量メモリ管理ソフト「<a href="http://www.vector.co.jp/soft/win95/hardware/se307525.html" target="_blank">びーめむLT</a>」 あのBeMemを超軽量化!</p>
<p>開発はC++Builder5を使用しています。本格的な構成になっており、高速に動作します。別途DLLは不要。<br />
ファイルサイズは大き目ですが、比べて常駐サイズは非常に小さくなっているのも特徴です。</p>
<p>BeMemLTはとにかく「軽い」ソフトを目指しました。ただし、必要な機能は削らない。中低機能マシン向けチューニングです。</p>
<p>他と違う!ここまで出来る!ほとんどCPU占有せず軽い!<br />
BeMemLTの主な機能<br />
・メモリデフラグにより空きメモリを増加させます。中断機能はBeMemオリジナルの特徴でBeMemにも引き継がれています。<br />
・物理メモリ量、スワップファイル量、仮想メモリ量、全体の使用率、CPUの占有率、リソースを表示可能。<br />
・痒いところに手が届く、細かい自動化設定はBeMem同様。</p>
<p>「無機能」の事を堂々と「軽い」という時代は終わりました。<br />
きちんと使える軽量メモリ管理&amp;コンパクションソフトの本命</p>
<p>実際インストールしてみた感想ですが説明にもありますように、非常に軽量コンパクトにまとまっていて、ちょっと古めのメモリ不足がちなパソコンにお勧めです!!</p>
<p><OBJECT classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http://fpdownload.macromedia.com/get/flashplayer/current/swflash.cab" id="Player_e6f06a3d-ccce-464e-9a65-6eae065ad42c"  WIDTH="400px" HEIGHT="150px"> <PARAM NAME="movie" VALUE="http://ws.amazon.co.jp/widgets/q?ServiceVersion=20070822&#038;MarketPlace=JP&#038;ID=V20070822%2FJP%2Fa63sjsdao-22%2F8010%2Fe6f06a3d-ccce-464e-9a65-6eae065ad42c&#038;Operation=GetDisplayTemplate"><PARAM NAME="quality" VALUE="high"><PARAM NAME="bgcolor" VALUE="#FFFFFF"><PARAM NAME="allowscriptaccess" VALUE="always"><embed src="http://ws.amazon.co.jp/widgets/q?ServiceVersion=20070822&#038;MarketPlace=JP&#038;ID=V20070822%2FJP%2Fa63sjsdao-22%2F8010%2Fe6f06a3d-ccce-464e-9a65-6eae065ad42c&#038;Operation=GetDisplayTemplate" id="Player_e6f06a3d-ccce-464e-9a65-6eae065ad42c" quality="high" bgcolor="#ffffff" name="Player_e6f06a3d-ccce-464e-9a65-6eae065ad42c" allowscriptaccess="always"  type="application/x-shockwave-flash" align="middle" height="150px" width="400px"></embed></OBJECT> <NOSCRIPT><A HREF="http://ws.amazon.co.jp/widgets/q?ServiceVersion=20070822&#038;MarketPlace=JP&#038;ID=V20070822%2FJP%2Fa63sjsdao-22%2F8010%2Fe6f06a3d-ccce-464e-9a65-6eae065ad42c&#038;Operation=NoScript">Amazon.co.jp ウィジェット</A></NOSCRIPT></p>
]]></content:encoded>
			<wfw:commentRss>http://www.yuichi.ne.jp/jisava/2010/04/%e3%82%b5%e3%83%bc%e3%83%90%e3%83%bc%e3%83%a1%e3%83%a2%e3%83%aa%e4%b8%8d%e8%b6%b3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Apacheサーバー設定</title>
		<link>http://www.yuichi.ne.jp/jisava/2009/08/apache%e3%82%b5%e3%83%bc%e3%83%90%e3%83%bc%e8%a8%ad%e5%ae%9a/</link>
		<comments>http://www.yuichi.ne.jp/jisava/2009/08/apache%e3%82%b5%e3%83%bc%e3%83%90%e3%83%bc%e8%a8%ad%e5%ae%9a/#comments</comments>
		<pubDate>Wed, 05 Aug 2009 03:44:43 +0000</pubDate>
		<dc:creator>jisava</dc:creator>
				<category><![CDATA[Apacheサーバー設定]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[server]]></category>
		<category><![CDATA[website]]></category>
		<category><![CDATA[XAMPP]]></category>
		<category><![CDATA[サーバー]]></category>
		<category><![CDATA[設定]]></category>

		<guid isPermaLink="false">http://www.yuichi.ne.jp/jisava/?p=43</guid>
		<description><![CDATA[Apacheの設定では、websiteの設定方法など説明します。さてさて、website公開する場合index・・・・つまりホームページのトップページのことなんだけれど、どこにあるんでしょうか?xamppをデフォルトでインストールした場合、以下がwebsiteパスになります。
C:\xampp\htdocs
で・・C:\xampp\htdocsを開き、「xampp」「restricted」「forbidden」フォルダを残して後はすべて削除します。
websiteを公開する場合は、C:\xampp\htdocsにindex.htmlを置きます
ブログを公開する場合は、C:\xampp\htdocsにWordPressからダウンロードしたフォルダの中身だけアップロードします。
website、ブログ両方公開する場合は、C:\xampp\htdocsにindex.htmlを置きます。C:\xampp\htdocsにフォルダ新規作成してWordPressからダウンロードしたフォルダの中身だけアップロードします
早い話、どちらをメインページにするかってこと・・websiteかブログ・・あなたならどっち?
多分ブログメインの方のほうが、多いと思いますので話進めます。次におすすみください・・・・・ドメインの設定
 Apacheが起動しているならApacheを終了してから始めましょう。Apacheの設定は、「C:\xampp\apache\conf」で行います。Windowsテキストパッドでは文字コードなどの不都合がありますので、こちらのソフトで編集「TeraPad」
 んでもって「TeraPad」「表示」「編集モード」「html」でこちらの、「C:\xampp\apache\conf」を編集していきます。失敗しても良いようにconfをデスクトップにバックアップしてから始めた方が良いでしょう。
#
# This is the main Apache HTTP server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See &#60;URL:http://httpd.apache.org/docs/2.2/&#62; for detailed information.
# In particular, see
# &#60;URL:http://httpd.apache.org/docs/2.2/mod/directives.html&#62;
# for a discussion of each configuration directive.
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They&#8217;re here only as hints  [...]]]></description>
			<content:encoded><![CDATA[<p>Apacheの設定では、websiteの設定方法など説明します。さてさて、website公開する場合index・・・・つまりホームページのトップページのことなんだけれど、どこにあるんでしょうか?xamppをデフォルトでインストールした場合、以下がwebsiteパスになります。</p>
<p>C:\xampp\htdocs</p>
<p>で・・C:\xampp\htdocsを開き、「xampp」「restricted」「forbidden」フォルダを残して後はすべて削除します。</p>
<p>websiteを公開する場合は、C:\xampp\htdocsにindex.htmlを置きます</p>
<p>ブログを公開する場合は、C:\xampp\htdocsに<a title="wordpress" href="http://ja.wordpress.org/" target="_blank">WordPress</a>からダウンロードしたフォルダの中身だけアップロードします。</p>
<p>website、ブログ両方公開する場合は、C:\xampp\htdocsにindex.htmlを置きます。C:\xampp\htdocsにフォルダ新規作成して<a title="wordpress" href="http://ja.wordpress.org/" target="_blank">WordPress</a>からダウンロードしたフォルダの中身だけアップロードします</p>
<p>早い話、どちらをメインページにするかってこと・・websiteかブログ・・あなたならどっち?</p>
<p>多分ブログメインの方のほうが、多いと思いますので話進めます。次におすすみください・・・・<a title="ドメインの設定" href="http://www.yuichi.ne.jp/jisava/category/%e3%83%89%e3%83%a1%e3%82%a4%e3%83%b3%e3%81%ae%e8%a8%ad%e5%ae%9a/" target="_self">・ドメインの設定</a></p>
<p> Apacheが起動しているならApacheを終了してから始めましょう。Apacheの設定は、「C:\xampp\apache\conf」で行います。Windowsテキストパッドでは文字コードなどの不都合がありますので、こちらのソフトで編集「<a title="TeraPad" href="http://www5f.biglobe.ne.jp/~t-susumu/" target="_blank">TeraPad</a>」</p>
<p> んでもって「TeraPad」「表示」「編集モード」「html」でこちらの、「C:\xampp\apache\conf」を編集していきます。失敗しても良いようにconfをデスクトップにバックアップしてから始めた方が良いでしょう。</p>
<p>#<br />
# This is the main Apache HTTP server configuration file.  It contains the<br />
# configuration directives that give the server its instructions.<br />
# See &lt;<a href="http://httpd.apache.org/docs/2.2/">URL:http://httpd.apache.org/docs/2.2/</a>&gt; for detailed information.<br />
# In particular, see<br />
# &lt;<a href="http://httpd.apache.org/docs/2.2/mod/directives.html">URL:http://httpd.apache.org/docs/2.2/mod/directives.html</a>&gt;<br />
# for a discussion of each configuration directive.<br />
#<br />
# Do NOT simply read the instructions in here without understanding<br />
# what they do.  They&#8217;re here only as hints or reminders.  If you are unsure<br />
# consult the online docs. You have been warned. <br />
#<br />
# Configuration and logfile names: If the filenames you specify for many<br />
# of the server&#8217;s control files begin with &#8220;/&#8221; (or &#8220;drive:/&#8221; for Win32), the<br />
# server will use that explicit path.  If the filenames do *not* begin<br />
# with &#8220;/&#8221;, the value of ServerRoot is prepended &#8212; so &#8220;logs/foo.log&#8221;<br />
# with ServerRoot set to &#8220;Ｃ:/xampp/apache&#8221; will be interpreted by the<br />
# server as &#8220;Ｃ:/xampp/apache/logs/foo.log&#8221;.<br />
#<br />
# NOTE: Where filenames are specified, you must use forward slashes<br />
# instead of backslashes (e.g., &#8220;c:/apache&#8221; instead of &#8220;c:\apache&#8221;).<br />
# If a drive letter is omitted, the drive on which Apache.exe is located<br />
# will be used by default.  It is recommended that you always supply<br />
# an explicit drive letter in absolute paths, however, to avoid<br />
# confusion.<br />
#</p>
<p># ThreadsPerChild: constant number of worker threads in the server process<br />
# MaxRequestsPerChild: maximum  number of requests a server process serves<br />
ThreadsPerChild 250<br />
MaxRequestsPerChild  0</p>
<p>#<br />
# ServerRoot: The top of the directory tree under which the server&#8217;s<br />
# configuration, error, and log files are kept.<br />
#<br />
# Do not add a slash at the end of the directory path.  If you point<br />
# ServerRoot at a non-local disk, be sure to point the LockFile directive<br />
# at a local disk.  If you wish to share the same ServerRoot for multiple<br />
# httpd daemons, you will need to change at least LockFile and PidFile.<br />
#<br />
ServerRoot &#8220;Ｃ:/xampp/apache&#8221;<span style="color: #ff0000;">ここの設定を確認42行目</span></p>
<p>#<br />
# Listen: Allows you to bind Apache to specific IP addresses and/or<br />
# ports, instead of the default. See also the &lt;VirtualHost&gt;<br />
# directive.<br />
#<br />
# Change this to Listen on specific IP addresses as shown below to<br />
# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)<br />
#<br />
#Listen 12.34.56.78:80<br />
Listen 80</p>
<p>#<br />
# Dynamic Shared Object (DSO) Support<br />
#<br />
# To be able to use the functionality of a module which was built as a DSO you<br />
# have to place corresponding `LoadModule&#8217; lines at this location so the<br />
# directives contained in it are actually available _before_ they are used.<br />
# Statically compiled modules (those listed by `httpd -l&#8217;) do not need<br />
# to be loaded here.<br />
#<br />
# Example:<br />
# LoadModule foo_module modules/mod_foo.so<br />
#<br />
LoadModule actions_module modules/mod_actions.so<br />
LoadModule alias_module modules/mod_alias.so<br />
LoadModule asis_module modules/mod_asis.so<br />
LoadModule auth_basic_module modules/mod_auth_basic.so<br />
LoadModule auth_digest_module modules/mod_auth_digest.so<br />
LoadModule authn_alias_module modules/mod_authn_alias.so<br />
LoadModule authn_anon_module modules/mod_authn_anon.so<br />
LoadModule authn_dbd_module modules/mod_authn_dbd.so<br />
LoadModule authn_dbm_module modules/mod_authn_dbm.so<br />
LoadModule authn_default_module modules/mod_authn_default.so<br />
LoadModule authn_file_module modules/mod_authn_file.so<br />
#LoadModule authnz_ldap_module modules/mod_authnz_ldap.so<br />
LoadModule authz_dbm_module modules/mod_authz_dbm.so<br />
LoadModule authz_default_module modules/mod_authz_default.so<br />
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so<br />
LoadModule authz_host_module modules/mod_authz_host.so<br />
#LoadModule authz_owner_module modules/mod_authz_owner.so<br />
LoadModule authz_user_module modules/mod_authz_user.so<br />
LoadModule autoindex_module modules/mod_autoindex.so<br />
LoadModule cache_module modules/mod_cache.so<br />
#LoadModule disk_cache_module modules/mod_disk_cache.so<br />
#LoadModule file_cache_module modules/mod_file_cache.so<br />
LoadModule mem_cache_module modules/mod_mem_cache.so<br />
LoadModule cern_meta_module modules/mod_cern_meta.so<br />
LoadModule charset_lite_module modules/mod_charset_lite.so<br />
LoadModule cgi_module modules/mod_cgi.so<br />
LoadModule dav_module modules/mod_dav.so<br />
LoadModule dav_fs_module modules/mod_dav_fs.so<br />
LoadModule deflate_module modules/mod_deflate.so<br />
LoadModule dir_module modules/mod_dir.so<br />
#LoadModule dumpio_module modules/mod_dumpio.so<br />
LoadModule env_module modules/mod_env.so<br />
LoadModule expires_module modules/mod_expires.so<br />
LoadModule ext_filter_module modules/mod_ext_filter.so<br />
LoadModule headers_module modules/mod_headers.so<br />
LoadModule ident_module modules/mod_ident.so<br />
#LoadModule imagemap_module modules/mod_imagemap.so<br />
LoadModule include_module modules/mod_include.so<br />
LoadModule info_module modules/mod_info.so<br />
LoadModule isapi_module modules/mod_isapi.so<br />
LoadModule ldap_module modules/mod_ldap.so<br />
#LoadModule logio_module modules/mod_logio.so<br />
LoadModule log_config_module modules/mod_log_config.so<br />
#LoadModule log_forensic_module modules/mod_log_forensic.so<br />
LoadModule mime_module modules/mod_mime.so<br />
LoadModule mime_magic_module modules/mod_mime_magic.so<br />
LoadModule negotiation_module modules/mod_negotiation.so<br />
#LoadModule proxy_module modules/mod_proxy.so<br />
#LoadModule proxy_ajp_module modules/mod_proxy_ajp.so<br />
#LoadModule proxy_balancer_module modules/mod_proxy_balancer.so<br />
#LoadModule proxy_connect_module modules/mod_proxy_connect.so<br />
#LoadModule proxy_http_module modules/mod_proxy_http.so<br />
#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so<br />
LoadModule rewrite_module modules/mod_rewrite.so<br />
LoadModule setenvif_module modules/mod_setenvif.so<br />
LoadModule speling_module modules/mod_speling.so<br />
LoadModule status_module modules/mod_status.so<br />
LoadModule unique_id_module modules/mod_unique_id.so<br />
#LoadModule userdir_module modules/mod_userdir.so<br />
LoadModule usertrack_module modules/mod_usertrack.so<br />
#LoadModule version_module modules/mod_version.so<br />
LoadModule vhost_alias_module modules/mod_vhost_alias.so<br />
LoadModule ssl_module modules/mod_ssl.so</p>
<p>#LoadModule autoindex_color_module modules/mod_autoindex_color.so<br />
#LoadModule mysql_auth_module modules/mod_auth_mysql.so<br />
#LoadModule auth_remote_module modules/mod_auth_remote.so<br />
#LoadModule sspi_auth_module modules/mod_auth_sspi.so<br />
#LoadModule log_sql_module modules/mod_log_sql.so<br />
#LoadModule log_sql_mysql_module modules/mod_log_sql_mysql.so<br />
#&lt;IfModule ssl_module&gt;<br />
#    LoadModule log_sql_ssl_module modules/mod_log_sql_ssl.so<br />
#&lt;/IfModule&gt;<br />
#LoadModule proxy_html_module modules/mod_proxy_html.so<br />
#LoadModule xmlns_module modules/mod_xmlns.so<br />
#LoadModule proxy_xml_module modules/mod_proxy_xml.so<br />
#LoadModule bw_module modules/mod_bw.so</p>
<p>### SVN from XAMPP devel package ###<br />
#LoadModule dav_svn_module modules/mod_dav_svn.so<br />
#LoadModule authz_svn_module modules/mod_authz_svn.so</p>
<p># &#8216;Main&#8217; server configuration<br />
#<br />
# The directives in this section set up the values used by the &#8216;main&#8217;<br />
# server, which responds to any requests that aren&#8217;t handled by a<br />
# &lt;VirtualHost&gt; definition.  These values also provide defaults for<br />
# any &lt;VirtualHost&gt; containers you may define later in the file.<br />
#<br />
# All of these directives may appear inside &lt;VirtualHost&gt; containers,<br />
# in which case these default settings will be overridden for the<br />
# virtual host being defined.<br />
#</p>
<p>#<br />
# ServerAdmin: Your address, where problems with the server should be<br />
# e-mailed.  This address appears on some server-generated pages, such<br />
# as error documents.  e.g. ユーザー名@あなたのドメイン<span style="color: #ff0000;">ここの設定を確認164行目エラーページで表示されるメールの設定になります。設定有効にするには#を削除します</span><br />
#<br />
ServerAdmin ユーザー名@あなたのドメイン<span style="color: #ff0000;">ここの設定を確認166行目メールの設定になります</span></p>
<p>#<br />
# ServerName gives the name and port that the server uses to identify itself.<br />
# This can often be determined automatically, but we recommend you specify<br />
# it explicitly to prevent problems during startup.<br />
#<br />
# If your host doesn&#8217;t have a registered DNS name, enter its IP address here.<br />
#<br />
ServerName www.あなたのドメイン:80<span style="color: #ff0000;">ここの設定を確認<a title="ドメインの設定" href="http://www.yuichi.ne.jp/jisava/category/%e3%83%89%e3%83%a1%e3%82%a4%e3%83%b3%e3%81%ae%e8%a8%ad%e5%ae%9a/" target="_self">ドメインの設定</a>で取得した「url」175行目</span></p>
<p>#<br />
# DocumentRoot: The directory out of which you will serve your<br />
# documents. By default, all requests are taken from this directory, but<br />
# symbolic links and aliases may be used to point to other locations.<br />
#<br />
DocumentRoot &#8220;C:\xampp\htdocs&#8221;<span style="color: #ff0000;">ここの設定を確認182行目トップページの場所になります</span></p>
<p>#<br />
# Each directory to which Apache has access can be configured with respect<br />
# to which services and features are allowed and/or disabled in that<br />
# directory (and its subdirectories).<br />
#<br />
# First, we configure the &#8220;default&#8221; to be a very restrictive set of<br />
# features. <br />
#<br />
&lt;Directory /&gt;<br />
    Options FollowSymLinks<br />
    AllowOverride None<br />
    Order deny,allow<br />
    Deny from all<br />
&lt;/Directory&gt;</p>
<p>#<br />
# Note that from this point forward you must specifically allow<br />
# particular features to be enabled &#8211; so if something&#8217;s not working as<br />
# you might expect, make sure that you have specifically enabled it<br />
# below.<br />
#</p>
<p>#<br />
# This should be changed to whatever you set DocumentRoot to.<br />
#<br />
&lt;Directory &#8220;C:\xampp\htdocs&#8221;&gt;<span style="color: #ff0000;">ここの設定を確認209行目トップページの場所になります<br />
</span>#<br />
    # Possible values for the Options directive are &#8220;None&#8221;, &#8220;All&#8221;,<br />
    # or any combination of:<br />
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews<br />
    #<br />
    # Note that &#8220;MultiViews&#8221; must be named *explicitly* &#8212; &#8220;Options All&#8221;<br />
    # doesn&#8217;t give it to you.<br />
    #<br />
    # The Options directive is both complicated and important.  Please see<br />
    # <a href="http://httpd.apache.org/docs/2.2/mod/core.html#options">http://httpd.apache.org/docs/2.2/mod/core.html#options</a><br />
    # for more information.<br />
    #<br />
    Options Indexes FollowSymLinks Includes ExecCGI<br />
  <br />
    #<br />
    # AllowOverride controls what directives may be placed in .htaccess files.<br />
    # It can be &#8220;All&#8221;, &#8220;None&#8221;, or any combination of the keywords:<br />
    #   Options FileInfo AuthConfig Limit<br />
    #<br />
    AllowOverride All</p>
<p>    #<br />
    # Controls who can get stuff from this server.<br />
    #<br />
    Order allow,deny<br />
    Allow from all</p>
<p>&lt;/Directory&gt;</p>
<p>#<br />
# DirectoryIndex: sets the file that Apache will serve if a directory<br />
# is requested.<br />
#<br />
&lt;IfModule dir_module&gt;<br />
    DirectoryIndex index.php index.php4 index.php3 index.cgi index.pl index.html index.htm index.shtml index.phtml<br />
&lt;/IfModule&gt;</p>
<p>#<br />
# The following lines prevent .htaccess and .htpasswd files from being<br />
# viewed by Web clients.<br />
#<br />
&lt;FilesMatch &#8220;^\.ht&#8221;&gt;<br />
    Order allow,deny<br />
    Deny from all<br />
&lt;/FilesMatch&gt;</p>
<p>#<br />
# ErrorLog: The location of the error log file.<br />
# If you do not specify an ErrorLog directive within a &lt;VirtualHost&gt;<br />
# container, error messages relating to that virtual host will be<br />
# logged here.  If you *do* define an error logfile for a &lt;VirtualHost&gt;<br />
# container, that host&#8217;s errors will be logged there and not here.<br />
#<br />
ErrorLog logs/error.log</p>
<p>#<br />
# LogLevel: Control the number of messages logged to the error_log.<br />
# Possible values include: debug, info, notice, warn, error, crit,<br />
# alert, emerg.<br />
#<br />
LogLevel warn</p>
<p>&lt;IfModule log_config_module&gt;<br />
    #<br />
    # The following directives define some format nicknames for use with<br />
    # a CustomLog directive (see below).<br />
    #<br />
    LogFormat &#8220;%h %l %u %t \&#8221;%r\&#8221; %&gt;s %b \&#8221;%{Referer}i\&#8221; \&#8221;%{User-Agent}i\&#8221;" combined<br />
    LogFormat &#8220;%h %l %u %t \&#8221;%r\&#8221; %&gt;s %b&#8221; common</p>
<p>    &lt;IfModule logio_module&gt;<br />
      # You need to enable mod_logio.c to use %I and %O<br />
      LogFormat &#8220;%h %l %u %t \&#8221;%r\&#8221; %&gt;s %b \&#8221;%{Referer}i\&#8221; \&#8221;%{User-Agent}i\&#8221; %I %O&#8221; combinedio<br />
    &lt;/IfModule&gt;</p>
<p>    #<br />
    # The location and format of the access logfile (Common Logfile Format).<br />
    # If you do not define any access logfiles within a &lt;VirtualHost&gt;<br />
    # container, they will be logged here.  Contrariwise, if you *do*<br />
    # define per-&lt;VirtualHost&gt; access logfiles, transactions will be<br />
    # logged therein and *not* in this file.<br />
    #<br />
    CustomLog logs/access.log common</p>
<p>    #<br />
    # If you prefer a logfile with access, agent, and referer information<br />
    # (Combined Logfile Format) you can use the following directive.<br />
    #<br />
    #CustomLog logs/access.log combined<br />
&lt;/IfModule&gt;</p>
<p>&lt;IfModule alias_module&gt;<br />
    #<br />
    # Redirect: Allows you to tell clients about documents that used to<br />
    # exist in your server&#8217;s namespace, but do not anymore. The client<br />
    # will make a new request for the document at its new location.<br />
    # Example:<br />
    # Redirect permanent /foo <a href="http://www.example.com/bar">http://www.example.com/bar</a></p>
<p>    #<br />
    # Alias: Maps web paths into filesystem paths and is used to<br />
    # access content that does not live under the DocumentRoot.<br />
    # Example:<br />
    # Alias /webpath /full/filesystem/path<br />
    #<br />
    # If you include a trailing / on /webpath then the server will<br />
    # require it to be present in the URL.  You will also likely<br />
    # need to provide a &lt;Directory&gt; section to allow access to<br />
    # the filesystem path.</p>
<p>    #<br />
    # ScriptAlias: This controls which directories contain server scripts.<br />
    # ScriptAliases are essentially the same as Aliases, except that<br />
    # documents in the target directory are treated as applications and<br />
    # run by the server when requested rather than as documents sent to the<br />
    # client.  The same rules about trailing &#8220;/&#8221; apply to ScriptAlias<br />
    # directives as to Alias.<br />
    #<br />
    ScriptAlias /cgi-bin/ &#8220;C:/xampp/htdocs/cgi-bin/&#8221;<span style="color: #ff0000;">ここの設定を確認328行目cgiスクリプト置く場所になります。C:/xampp/htdocs/にcgi-binフォルダ作って下さい</span></p>
<p>&lt;/IfModule&gt;</p>
<p>#<br />
# &#8220;C:/xampp/cgi-bin&#8221; should be changed to whatever your ScriptAliased<br />
# CGI directory exists, if you have that configured.<br />
#<br />
&lt;Directory &#8220;C:/xampp/htdocs/cgi-bin&#8221;&gt;<span style="color: #ff0000;">ここの設定を確認336行目</span><br />
    AllowOverride None<br />
    Options None<br />
    Order allow,deny<br />
    Allow from all<br />
&lt;/Directory&gt;</p>
<p>#<br />
# Apache parses all CGI scripts for the shebang line by default.<br />
# This comment line, the first line of the script, consists of the symbols<br />
# pound (#) and exclamation (!) followed by the path of the program that<br />
# can execute this specific script.  For a perl script, with perl.exe in<br />
# the C:\Program Files\Perl directory, the shebang line should be:</p>
<p>   #!C:\xampp\perl</p>
<p># Note you _must_not_ indent the actual shebang line, and it must be the<br />
# first line of the file.  Of course, CGI processing must be enabled by<br />
# the appropriate ScriptAlias or Options ExecCGI directives for the files<br />
# or directory in question.<br />
#<br />
# However, Apache on Windows allows either the Unix behavior above, or can<br />
# use the Registry to match files by extention.  The command to execute<br />
# a file of this type is retrieved from the registry by the same method as<br />
# the Windows Explorer would use to handle double-clicking on a file.<br />
# These script actions can be configured from the Windows Explorer View menu,<br />
# &#8216;Folder Options&#8217;, and reviewing the &#8216;File Types&#8217; tab.  Clicking the Edit<br />
# button allows you to modify the Actions, of which Apache 1.3 attempts to<br />
# perform the &#8216;Open&#8217; Action, and failing that it will try the shebang line.<br />
# This behavior is subject to change in Apache release 2.0.<br />
#<br />
# Each mechanism has it&#8217;s own specific security weaknesses, from the means<br />
# to run a program you didn&#8217;t intend the website owner to invoke, and the<br />
# best method is a matter of great debate.<br />
#<br />
# To enable the this Windows specific behavior (and therefore -disable- the<br />
# equivilant Unix behavior), uncomment the following directive:<br />
#<br />
#ScriptInterpreterSource registry<br />
#<br />
# The directive above can be placed in individual &lt;Directory&gt; blocks or the<br />
# .htaccess file, with either the &#8216;registry&#8217; (Windows behavior) or &#8217;script&#8217;<br />
# (Unix behavior) option, and will override this server default option.<br />
#</p>
<p>#<br />
# DefaultType: the default MIME type the server will use for a document<br />
# if it cannot otherwise determine one, such as from filename extensions.<br />
# If your server contains mostly text or HTML documents, &#8220;text/plain&#8221; is<br />
# a good value.  If most of your content is binary, such as applications<br />
# or images, you may want to use &#8220;application/octet-stream&#8221; instead to<br />
# keep browsers from trying to display binary files as though they are<br />
# text.<br />
#<br />
DefaultType text/plain</p>
<p>&lt;IfModule mime_module&gt;<br />
    #<br />
    # TypesConfig points to the file containing the list of mappings from<br />
    # filename extension to MIME-type.<br />
    #<br />
    TypesConfig conf/mime.types</p>
<p>    #<br />
    # AddType allows you to add to or override the MIME configuration<br />
    # file specified in TypesConfig for specific file types.<br />
    #<br />
    #AddType application/x-gzip .tgz<br />
    #<br />
    # AddEncoding allows you to have certain browsers uncompress<br />
    # information on the fly. Note: Not all browsers support this.<br />
    #<br />
    #AddEncoding x-compress .Z<br />
    #AddEncoding x-gzip .gz .tgz<br />
    #<br />
    # If the AddEncoding directives above are commented-out, then you<br />
    # probably should define those extensions to indicate media types:<br />
    #<br />
    AddType application/x-compress .Z<br />
    AddType application/x-gzip .gz .tgz</p>
<p>    #<br />
    # AddHandler allows you to map certain file extensions to &#8220;handlers&#8221;:<br />
    # actions unrelated to filetype. These can be either built into the server<br />
    # or added with the Action directive (see below)<br />
    #<br />
    # To use CGI scripts outside of ScriptAliased directories:<br />
    # (You will also need to add &#8220;ExecCGI&#8221; to the &#8220;Options&#8221; directive.)<br />
    #<br />
    AddHandler cgi-script .cgi</p>
<p>    # For files that include their own HTTP headers:<br />
    #AddHandler send-as-is asis</p>
<p>    # For server-parsed imagemap files:<br />
    #AddHandler imap-file map</p>
<p>    # For type maps (negotiated resources):<br />
    #AddHandler type-map var</p>
<p>    #<br />
    # Filters allow you to process content before it is sent to the client.<br />
    #<br />
    # To parse .shtml files for server-side includes (SSI):<br />
    # (You will also need to add &#8220;Includes&#8221; to the &#8220;Options&#8221; directive.)<br />
    #<br />
   AddType text/html .shtml<br />
   AddOutputFilter INCLUDES .shtml<br />
&lt;/IfModule&gt;</p>
<p>#<br />
# The mod_mime_magic module allows the server to use various hints from the<br />
# contents of the file itself to determine its type.  The MIMEMagicFile<br />
# directive tells the module where the hint definitions are located.<br />
#<br />
#MIMEMagicFile conf/magic</p>
<p>#<br />
# Customizable error responses come in three flavors:<br />
# 1) plain text 2) local redirects 3) external redirects<br />
#<br />
# Some examples:<br />
#ErrorDocument 500 &#8220;The server made a boo boo.&#8221;<br />
#ErrorDocument 404 /missing.html<br />
#ErrorDocument 404 &#8220;/cgi-bin/missing_handler.pl&#8221;<br />
#ErrorDocument 402 <a href="http://www.example.com/subscription_info.html">http://www.example.com/subscription_info.html</a><br />
#</p>
<p>#<br />
# EnableMMAP and EnableSendfile: On systems that support it,<br />
# memory-mapping or the sendfile syscall is used to deliver<br />
# files.  This usually improves server performance, but must<br />
# be turned off when serving from networked-mounted<br />
# filesystems or if support for these functions is otherwise<br />
# broken on your system.<br />
#<br />
EnableMMAP off<br />
EnableSendfile off</p>
<p># Supplemental configuration<br />
#<br />
# The configuration files in the conf/extra/ directory can be<br />
# included to add extra features or to modify the default configuration of<br />
# the server, or you may simply copy their contents here and change as<br />
# necessary.</p>
<p># XAMPP specific settings<br />
Include conf/extra/httpd-xampp.conf</p>
<p># Server-pool management (MPM specific)<br />
# Include conf/extra/httpd-mpm.conf</p>
<p># Multi-language error messages<br />
Include conf/extra/httpd-multilang-errordoc.conf</p>
<p># Fancy directory listings<br />
Include conf/extra/httpd-autoindex.conf</p>
<p># Language settings<br />
Include conf/extra/httpd-languages.conf</p>
<p># User home directories<br />
Include conf/extra/httpd-userdir.conf</p>
<p># Real-time info on requests and configuration<br />
Include conf/extra/httpd-info.conf</p>
<p># Virtual hosts<br />
Include conf/extra/httpd-vhosts.conf</p>
<p># Local access to the Apache HTTP Server Manual<br />
Include conf/extra/httpd-manual.conf</p>
<p># Distributed authoring and versioning (WebDAV)<br />
Include conf/extra/httpd-dav.conf</p>
<p># Various default settings<br />
Include conf/extra/httpd-default.conf</p>
<p># Secure (SSL/TLS) connections<br />
Include conf/extra/httpd-ssl.conf</p>
<p>#<br />
# Note: The following must must be present to support<br />
#       starting without SSL on platforms with no /dev/random equivalent<br />
#       but a statically compiled-in mod_ssl.<br />
#<br />
&lt;IfModule ssl_module&gt;<br />
SSLRandomSeed startup builtin<br />
SSLRandomSeed connect builtin<br />
&lt;/IfModule&gt;</p>
<p> Apacheの設定終了</p>
<p>さていよいよ<a title="ドメインの設定" href="http://www.yuichi.ne.jp/jisava/category/%e3%83%89%e3%83%a1%e3%82%a4%e3%83%b3%e3%81%ae%e8%a8%ad%e5%ae%9a/" target="_self">ドメインの設定</a>で取得したアドレスでアクセスできるか確認してみます。<a title="自宅サーバー開設準備2" href="http://www.yuichi.ne.jp/jisava/2009/08/%e8%87%aa%e5%ae%85%e3%82%b5%e3%83%bc%e3%83%90%e3%83%bc%e9%96%8b%e8%a8%ad%e6%ba%96%e5%82%992/" target="_self">XAMPP Control Panel</a>を開きApacheが起動している事を確認。<a title="ドメインの設定" href="http://www.yuichi.ne.jp/jisava/2009/08/%e3%83%89%e3%83%a1%e3%82%a4%e3%83%b3%e3%81%ae%e8%a8%ad%e5%ae%9a/" target="_self">dice</a>が起動している事を確認。どうでしょうか?DynamicDNSの場合、サーバー起動してからurl表示されるまで15分ほどかかります。無事に表示された方はおめでとうございます。アクセス出来ない方はたぶんポートが開放されていないと思うので<a title="ファイアウォール設定" href="http://www.yuichi.ne.jp/jisava/2009/08/%e3%83%95%e3%82%a1%e3%82%a4%e3%82%a2%e3%82%a6%e3%82%a9%e3%83%bc%e3%83%ab%e8%a8%ad%e5%ae%9a/" target="_self">ファイアウォール設定</a>で確認してください</p>
<p><OBJECT classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http://fpdownload.macromedia.com/get/flashplayer/current/swflash.cab" id="Player_93a650d0-789e-49d0-83b3-78284e199495"  WIDTH="600px" HEIGHT="200px"> <PARAM NAME="movie" VALUE="http://ws.amazon.co.jp/widgets/q?ServiceVersion=20070822&#038;MarketPlace=JP&#038;ID=V20070822%2FJP%2Fa63sjsdao-22%2F8010%2F93a650d0-789e-49d0-83b3-78284e199495&#038;Operation=GetDisplayTemplate"><PARAM NAME="quality" VALUE="high"><PARAM NAME="bgcolor" VALUE="#FFFFFF"><PARAM NAME="allowscriptaccess" VALUE="always"><embed src="http://ws.amazon.co.jp/widgets/q?ServiceVersion=20070822&#038;MarketPlace=JP&#038;ID=V20070822%2FJP%2Fa63sjsdao-22%2F8010%2F93a650d0-789e-49d0-83b3-78284e199495&#038;Operation=GetDisplayTemplate" id="Player_93a650d0-789e-49d0-83b3-78284e199495" quality="high" bgcolor="#ffffff" name="Player_93a650d0-789e-49d0-83b3-78284e199495" allowscriptaccess="always"  type="application/x-shockwave-flash" align="middle" height="200px" width="600px"></embed></OBJECT> <NOSCRIPT><A HREF="http://ws.amazon.co.jp/widgets/q?ServiceVersion=20070822&#038;MarketPlace=JP&#038;ID=V20070822%2FJP%2Fa63sjsdao-22%2F8010%2F93a650d0-789e-49d0-83b3-78284e199495&#038;Operation=NoScript">Amazon.co.jp ウィジェット</A></NOSCRIPT></p>
]]></content:encoded>
			<wfw:commentRss>http://www.yuichi.ne.jp/jisava/2009/08/apache%e3%82%b5%e3%83%bc%e3%83%90%e3%83%bc%e8%a8%ad%e5%ae%9a/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

