archive-de.com » DE » K » KW-BERLIN.DE

Total: 256

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Site Map - Apache HTTP サーバ
    ユーザ毎のウェブディレクトリ プラットフォーム固有の情報 概略 Microsoft Windows での Apache の使用 Microsoft Windows での Apache のコンパイル Novell NetWare で Apache を使う HPUX で高性能ウェブサーバを実行する EBCDIC 版 Apache Apache HTTP サーバとサポートプログラム 概略 マニュアルページ httpd マニュアルページ ab マニュアルページ apachectl マニュアルページ apxs マニュアルページ configure マニュアルページ dbmmanage マニュアルページ htcacheclean マニュアルページ htdbm マニュアルページ htdigest マニュアルページ htpasswd マニュアルページ logresolve マニュアルページ rotatelogs マニュアルページ suexec 他のプログラム Apache その他 概略 関連する標準規格 Apache モジュール Apache ディレクティブの説明に使われる用語 Apache ディレクティブを説明に使われる用語 Apache コア機能 Apache MPM 共通ディレクティブ Apache MPM beos Apache MPM event Apache MPM netware Apache MPM os2 Apache MPM prefork Apache MPM winnt Apache MPM worker Apache モジュール mod actions Apache モジュール mod alias Apache モジュール mod asis Apache モジュール mod auth basic Apache モジュール mod auth digest Apache モジュール mod authn alias Apache モジュール mod authn anon Apache モジュール mod authn dbd Apache モジュール mod authn dbm Apache モジュール mod authn default Apache モジュール mod authn file Apache モジュール mod authnz ldap Apache モジュール mod authz dbm Apache モジュール mod authz default Apache モジュール mod authz groupfile Apache モジュール mod authz host Apache モジュール mod authz owner Apache モジュール mod authz user Apache モジュール mod autoindex Apache モジュール mod cache Apache モジュール mod cern meta Apache モジュール mod cgi Apache モジュール mod cgid Apache モジュール mod charset lite Apache モジュール mod dav Apache モジュール mod dav fs Apache モジュール mod dav lock Apache モジュール mod dbd Apache モジュール mod deflate Apache モジュール mod dir Apache モジュール mod disk cache Apache モジュール mod dumpio Apache モジュール mod echo Apache モジュール mod env Apache モジュール mod example Apache モジュール mod expires Apache モジュール mod ext filter Apache モジュール mod file cache Apache モジュール mod filter Apache モジュール mod headers Apache モジュール mod ident Apache モジュール mod imagemap Apache モジュール mod include Apache モジュール mod info Apache モジュール mod isapi Apache モジュール mod ldap Apache モジュール mod log

    Original URL path: http://xserve.kw-berlin.de/manual/ja/sitemap.html (2016-02-16)
    Open archived version from archive


  • 사이트맵 - Apache HTTP Server
    인증 CGI로 동적 페이지 생성 Server Side Includes 소개 htaccess 파일 사용자별 웹디렉토리 플래폼별 설명 개요 Microsoft Windows에서 아파치 사용하기 Microsoft Windows에서 아파치 컴파일하기 Novell NetWare에서 아파치 사용하기 HPUX에서 고성능 웹서버 실행하기 아파치 EBCDIC 포팅 아파치 웹서버와 지원 프로그램 개요 Manpage httpd Manpage ab Manpage apachectl Manpage apxs Manpage configure Manpage dbmmanage Manpage htcacheclean Manpage htdigest Manpage htpasswd Manpage logresolve Manpage rotatelogs Manpage suexec 다른 프로그램들 기타 아파치 문서 개요 관련된 표준들 아파치 모듈 아파치 모듈을 설명하는데 사용한 용어정의 아파치 지시어를 설명하는데 사용한 용어정의 아파치 핵심 기능 아파치 MPM 공통 지시어 아파치 MPM beos 아파치 MPM event 아파치 MPM netware 아파치 MPM os2 아파치 MPM prefork 아파치 MPM winnt 아파치 MPM worker 아파치 모듈 mod actions 아파치 모듈 mod alias 아파치 모듈 mod asis 아파치 모듈 mod auth basic 아파치 모듈 mod auth digest 아파치 모듈 mod authn alias 아파치 모듈 mod authn anon 아파치 모듈 mod authn dbd 아파치 모듈 mod authn dbm 아파치 모듈 mod authn default 아파치 모듈 mod authn file 아파치 모듈 mod authnz ldap 아파치 모듈 mod authz dbm 아파치 모듈 mod authz default 아파치 모듈 mod authz groupfile 아파치 모듈 mod authz host 아파치 모듈 mod authz owner 아파치 모듈 mod authz user 아파치 모듈 mod autoindex 아파치 모듈 mod cache 아파치 모듈 mod cern meta 아파치 모듈 mod cgi 아파치 모듈 mod cgid 아파치 모듈 mod charset lite 아파치 모듈 mod dav 아파치 모듈 mod dav fs 아파치 모듈 mod dav lock 아파치 모듈 mod dbd 아파치 모듈 mod deflate 아파치 모듈 mod dir 아파치 모듈 mod disk cache 아파치 모듈 mod dumpio 아파치 모듈 mod echo 아파치 모듈 mod env 아파치 모듈 mod example 아파치 모듈 mod expires 아파치 모듈 mod ext filter 아파치 모듈 mod file cache 아파치 모듈 mod filter 아파치 모듈 mod headers 아파치 모듈 mod ident 아파치 모듈

    Original URL path: http://xserve.kw-berlin.de/manual/ko/sitemap.html (2016-02-16)
    Open archived version from archive

  • Custom Error Responses - Apache HTTP Server
    I HP UX A 09 05 9000 712 REDIRECT PATH bin usr local bin etc REDIRECT QUERY STRING REDIRECT REMOTE ADDR 121 345 78 123 REDIRECT REMOTE HOST ooh ahhh com REDIRECT SERVER NAME crash bang edu REDIRECT SERVER PORT 80 REDIRECT SERVER SOFTWARE Apache 0 8 15 REDIRECT URL cgi bin buggy pl Note the REDIRECT prefix At least REDIRECT URL and REDIRECT QUERY STRING will be passed to the new URL assuming it s a cgi script or a cgi include The other variables will exist only if they existed prior to the error problem None of these will be set if your ErrorDocument is an external redirect anything starting with a scheme name like http even if it refers to the same host as the server Configuration Use of ErrorDocument is enabled for htaccess files when the AllowOverride is set accordingly Here are some examples ErrorDocument 500 cgi bin crash recover ErrorDocument 500 Sorry our script crashed Oh dear ErrorDocument 500 http xxx ErrorDocument 404 Lame excuses not found html ErrorDocument 401 Subscription how to subscribe html The syntax is ErrorDocument 3 digit code action where the action can be Text to be displayed Wrap the text with quotes An external URL to redirect to A local URL to redirect to Custom Error Responses and Redirects Apache s behavior to redirected URLs has been modified so that additional environment variables are available to a script server include Old behavior Standard CGI vars were made available to a script which has been redirected to No indication of where the redirection came from was provided New behavior A new batch of environment variables will be initialized for use by a script which has been redirected to Each new variable will have the prefix REDIRECT REDIRECT environment variables are created

    Original URL path: http://xserve.kw-berlin.de/manual/custom-error.html (2016-02-16)
    Open archived version from archive

  • Name-based Virtual Host Support - Apache HTTP Server
    not automatically make the server listen to that IP address See Setting which addresses and ports Apache uses for more details In addition any IP address specified here must be associated with a network interface on the server The next step is to create a VirtualHost block for each different host that you would like to serve The argument to the VirtualHost directive must match a defined NameVirtualHost directive In this usual case this will be 80 Inside each VirtualHost block you will need at minimum a ServerName directive to designate which host is served and a DocumentRoot directive to show where in the filesystem the content for that host lives Main host goes away If you are adding virtual hosts to an existing web server you must also create a VirtualHost block for the existing host The ServerName and DocumentRoot included in this virtual host should be the same as the global ServerName and DocumentRoot List this virtual host first in the configuration file so that it will act as the default host For example suppose that you are serving the domain www domain tld and you wish to add the virtual host www otherdomain tld which points at the same IP address Then you simply add the following to httpd conf NameVirtualHost 80 VirtualHost 80 ServerName www domain tld ServerAlias domain tld domain tld DocumentRoot www domain VirtualHost VirtualHost 80 ServerName www otherdomain tld DocumentRoot www otherdomain VirtualHost You can alternatively specify an explicit IP address in place of the in both the NameVirtualHost and VirtualHost directives For example you might want to do this in order to run some name based virtual hosts on one IP address and either IP based or another set of name based virtual hosts on another address Many servers want to be accessible by more than one name This is possible with the ServerAlias directive placed inside the VirtualHost section For example in the first VirtualHost block above the ServerAlias directive indicates that the listed names are other names which people can use to see that same web site ServerAlias domain tld domain tld then requests for all hosts in the domain tld domain will be served by the www domain tld virtual host The wildcard characters and can be used to match names Of course you can t just make up names and place them in ServerName or ServerAlias You must first have your DNS server properly configured to map those names to an IP address associated with your server Finally you can fine tune the configuration of the virtual hosts by placing other directives inside the VirtualHost containers Most directives can be placed in these containers and will then change the configuration only of the relevant virtual host To find out if a particular directive is allowed check the Context of the directive Configuration directives set in the main server context outside any VirtualHost container will be used only if they are not overridden by the virtual host settings Now

    Original URL path: http://xserve.kw-berlin.de/manual/vhosts/name-based.html (2016-02-16)
    Open archived version from archive

  • Apache IP-based Virtual Host Support - Apache HTTP Server
    are security partitioning issues such as company1 does not want anyone at company2 to be able to read their data except via the web In this case you would need two daemons each running with different User Group Listen and ServerRoot settings You can afford the memory and file descriptor requirements of listening to every IP alias on the machine It s only possible to Listen to the wildcard address or to specific addresses So if you have a need to listen to a specific address for whatever reason then you will need to listen to all specific addresses Although one httpd could listen to N 1 of the addresses and another could listen to the remaining address Use a single daemon when Sharing of the httpd configuration between virtual hosts is acceptable The machine services a large number of requests and so the performance loss in running separate daemons may be significant Setting up multiple daemons Create a separate httpd installation for each virtual host For each installation use the Listen directive in the configuration file to select which IP address or virtual host that daemon services e g Listen www smallco com 80 It is recommended that you use an IP address instead of a hostname see DNS caveats Setting up a single daemon with virtual hosts For this case a single httpd will service requests for the main server and all the virtual hosts The VirtualHost directive in the configuration file is used to set the values of ServerAdmin ServerName DocumentRoot ErrorLog and TransferLog or CustomLog configuration directives to different values for each virtual host e g VirtualHost www smallco com ServerAdmin webmaster mail smallco com DocumentRoot groups smallco www ServerName www smallco com ErrorLog groups smallco logs error log TransferLog groups smallco logs access log VirtualHost

    Original URL path: http://xserve.kw-berlin.de/manual/vhosts/ip-based.html (2016-02-16)
    Open archived version from archive

  • Dynamically configured mass virtual hosting - Apache HTTP Server
    over by another module either mod vhost alias or mod rewrite which has a different way of doing the mapping Neither of these modules is responsible for setting the DOCUMENT ROOT environment variable so if any CGIs or SSI documents make use of it they will get a misleading value Simple dynamic virtual hosts This extract from httpd conf implements the virtual host arrangement outlined in the Motivation section above but in a generic fashion using mod vhost alias get the server name from the Host header UseCanonicalName Off this log format can be split per virtual host based on the first field LogFormat V h l u t r s b vcommon CustomLog logs access log vcommon include the server name in the filenames used to satisfy requests VirtualDocumentRoot www hosts 0 docs VirtualScriptAlias www hosts 0 cgi bin This configuration can be changed into an IP based virtual hosting solution by just turning UseCanonicalName Off into UseCanonicalName DNS The server name that is inserted into the filename is then derived from the IP address of the virtual host A virtually hosted homepages system This is an adjustment of the above system tailored for an ISP s homepages server Using a slightly more complicated configuration we can select substrings of the server name to use in the filename so that e g the documents for www user isp com are found in home user It uses a single cgi bin directory instead of one per virtual host all the preliminary stuff is the same as above then include part of the server name in the filenames VirtualDocumentRoot www hosts 2 docs single cgi bin directory ScriptAlias cgi bin www std cgi There are examples of more complicated VirtualDocumentRoot settings in the mod vhost alias documentation Using more than one virtual hosting system on the same server With more complicated setups you can use Apache s normal VirtualHost directives to control the scope of the various virtual hosting configurations For example you could have one IP address for homepages customers and another for commercial customers with the following setup This can of course be combined with conventional VirtualHost configuration sections UseCanonicalName Off LogFormat V h l u t r s b vcommon Directory www commercial Options FollowSymLinks AllowOverride All Directory Directory www homepages Options FollowSymLinks AllowOverride None Directory VirtualHost 111 22 33 44 ServerName www commercial isp com CustomLog logs access log commercial vcommon VirtualDocumentRoot www commercial 0 docs VirtualScriptAlias www commercial 0 cgi bin VirtualHost VirtualHost 111 22 33 45 ServerName www homepages isp com CustomLog logs access log homepages vcommon VirtualDocumentRoot www homepages 0 docs ScriptAlias cgi bin www std cgi VirtualHost Note If the first VirtualHost block does not include a ServerName directive the reverse DNS of the relevant IP will be used instead If this is not the server name you wish to use a bogus entry ServerName none example com can be added to get around this behaviour More efficient IP based virtual hosting After

    Original URL path: http://xserve.kw-berlin.de/manual/vhosts/mass.html (2016-02-16)
    Open archived version from archive

  • VirtualHost Examples - Apache HTTP Server
    rather than the fully qualified host name server example com Note also that in the above example you can replace the list of IP addresses with which will cause the server to respond the same on all addresses Running different sites on different ports You have multiple domains going to the same IP and also want to serve multiple ports By defining the ports in the NameVirtualHost tag you can allow this to work If you try using VirtualHost name port without the NameVirtualHost name port or you try to use the Listen directive your configuration will not work Server configuration Listen 80 Listen 8080 NameVirtualHost 172 20 30 40 80 NameVirtualHost 172 20 30 40 8080 VirtualHost 172 20 30 40 80 ServerName www example com DocumentRoot www domain 80 VirtualHost VirtualHost 172 20 30 40 8080 ServerName www example com DocumentRoot www domain 8080 VirtualHost VirtualHost 172 20 30 40 80 ServerName www example org DocumentRoot www otherdomain 80 VirtualHost VirtualHost 172 20 30 40 8080 ServerName www example org DocumentRoot www otherdomain 8080 VirtualHost IP based virtual hosting The server has two IP addresses 172 20 30 40 and 172 20 30 50 which resolve to the names www example com and www example org respectively Server configuration Listen 80 VirtualHost 172 20 30 40 DocumentRoot www example1 ServerName www example com VirtualHost VirtualHost 172 20 30 50 DocumentRoot www example2 ServerName www example org VirtualHost Requests for any address not specified in one of the VirtualHost directives such as localhost for example will go to the main server if there is one Mixed port based and ip based virtual hosts The server machine has two IP addresses 172 20 30 40 and 172 20 30 50 which resolve to the names www example com and www example org respectively In each case we want to run hosts on ports 80 and 8080 Server configuration Listen 172 20 30 40 80 Listen 172 20 30 40 8080 Listen 172 20 30 50 80 Listen 172 20 30 50 8080 VirtualHost 172 20 30 40 80 DocumentRoot www example1 80 ServerName www example com VirtualHost VirtualHost 172 20 30 40 8080 DocumentRoot www example1 8080 ServerName www example com VirtualHost VirtualHost 172 20 30 50 80 DocumentRoot www example2 80 ServerName www example org VirtualHost VirtualHost 172 20 30 50 8080 DocumentRoot www example2 8080 ServerName www example org VirtualHost Mixed name based and IP based vhosts On some of my addresses I want to do name based virtual hosts and on others IP based hosts Server configuration Listen 80 NameVirtualHost 172 20 30 40 VirtualHost 172 20 30 40 DocumentRoot www example1 ServerName www example com VirtualHost VirtualHost 172 20 30 40 DocumentRoot www example2 ServerName www example org VirtualHost VirtualHost 172 20 30 40 DocumentRoot www example3 ServerName www example3 net VirtualHost IP based VirtualHost 172 20 30 50 DocumentRoot www example4 ServerName www example4 edu VirtualHost VirtualHost 172 20 30 60 DocumentRoot www example5 ServerName

    Original URL path: http://xserve.kw-berlin.de/manual/vhosts/examples.html (2016-02-16)
    Open archived version from archive

  • An In-Depth Discussion of Virtual Host Matching - Apache HTTP Server
    this final merging occurs So even if a main server definition appears after a vhost definition it might affect the vhost definition If the main server has no ServerName at this point then the hostname of the machine that httpd is running on is used instead We will call the main server address set those IP addresses returned by a DNS lookup on the ServerName of the main server For any undefined ServerName fields a name based vhost defaults to the address given first in the VirtualHost statement defining the vhost Any vhost that includes the magic default wildcard is given the same ServerName as the main server Virtual Host Matching The server determines which vhost to use for a request as follows Hash table lookup When the connection is first made by a client the IP address to which the client connected is looked up in the internal IP hash table If the lookup fails the IP address wasn t found the request is served from the default vhost if there is such a vhost for the port to which the client sent the request If there is no matching default vhost the request is served from the main server If the IP address is not found in the hash table then the match against the port number may also result in an entry corresponding to a NameVirtualHost which is subsequently handled like other name based vhosts If the lookup succeeded a corresponding list for the IP address was found the next step is to decide if we have to deal with an IP based or a name base vhost IP based vhost If the entry we found has an empty name list then we have found an IP based vhost no further actions are performed and the request is served from that vhost Name based vhost If the entry corresponds to a name based vhost the name list contains one or more vhost structures This list contains the vhosts in the same order as the VirtualHost directives appear in the config file The first vhost on this list the first vhost in the config file with the specified IP address has the highest priority and catches any request to an unknown server name or a request without a Host header field If the client provided a Host header field the list is searched for a matching vhost and the first hit on a ServerName or ServerAlias is taken and the request is served from that vhost A Host header field can contain a port number but Apache always matches against the real port to which the client sent the request If the client submitted a HTTP 1 0 request without Host header field we don t know to what server the client tried to connect and any existing ServerPath is matched against the URI from the request The first matching path on the list is used and the request is served from that vhost If no matching vhost

    Original URL path: http://xserve.kw-berlin.de/manual/vhosts/details.html (2016-02-16)
    Open archived version from archive



  •