Net Форумы

 
 FAQFAQ   ПоискПоиск   ПользователиПользователи   ГруппыГруппы   РегистрацияРегистрация 
 ПрофильПрофиль   Войти и проверить личные сообщенияВойти и проверить личные сообщения   ВходВход 
Генеральный спонсор: www.Net.Ru - серьезный, профессиональный хостинг.

apache

 
Начать новую тему   Ответить на тему    Список форумов Net Форумы -> Apache настройки
Предыдущая тема :: Следующая тема  
Автор Сообщение
Korn
Member


Зарегистрирован: 01.01.1970
Сообщения: 15

СообщениеДобавлено: 22.05.2002 06:18    Заголовок сообщения: Ответить с цитатой

вот я включаю апачи у себя на компе, захожу на <!-- BBCode auto-link start --><a href="http://мой.ip" target="_blank">http://мой.ip</a><!-- BBCode auto-link end --> и у меня всё работает. <BR> <BR>можно ли как то сделать что бы вот я включаю апачи , захожу на <!-- BBCode auto-link start --><a href="http://www.мой-сайт.ru" target="_blank">http://www.мой-сайт.ru</a><!-- BBCode auto-link end --> и там всё работает, то что у меня лежит в html папке у себя на компе <BR> <BR>как это сделать? если вообще можно <BR> <BR>к примеру я хочу чат программу что бы на сайте работала, а ip у меня все время меняется при кажом подключении в инет <BR>
Вернуться к началу
Посмотреть профиль Отправить личное сообщение Посетить сайт автора
Korn
Member


Зарегистрирован: 01.01.1970
Сообщения: 15

СообщениеДобавлено: 22.05.2002 06:29    Заголовок сообщения: Ответить с цитатой

я просто ещё не очень разбираюсь во всем <IMG SRC="/images/smiles/icon_biggrin.gif"> <BR>это единственая вещь которую мне нужно узнать<BR><BR><font size=-1>[ Это Сообщение было отредактировано: Korn в 2002-05-22 20:28 ]</font>
Вернуться к началу
Посмотреть профиль Отправить личное сообщение Посетить сайт автора
СЕМЕН
Member


Зарегистрирован: 01.01.1970
Сообщения: 29

СообщениеДобавлено: 27.05.2002 00:36    Заголовок сообщения: Ответить с цитатой

Если ip все время меняется, то ничего не сделаешь. Нужен постоянный ip. Некоторые провайдеры предоставляют это отдельной услугой. <BR>
Вернуться к началу
Посмотреть профиль Отправить личное сообщение Посетить сайт автора
Korn
Member


Зарегистрирован: 01.01.1970
Сообщения: 15

СообщениеДобавлено: 27.05.2002 03:37    Заголовок сообщения: Ответить с цитатой

Дык даже если я зайду на <!-- BBCode auto-link start --><a href="http://мой-ip.ru" target="_blank">http://мой-ip.ru</a><!-- BBCode auto-link end --> с не фиксированным ip адресом, то тоже работать не будет? <BR> <BR> <BR>не скажите ли все ли я правильно сделал в конфиге? а то я мягко говоря уже подзае....ся с этим делом, у меня все работает а у тех кто заходит на ип нет: <BR> <BR># <BR># Based upon the NCSA server configuration files originally by Rob McCool. <BR># <BR># This is the main Apache server configuration file. It contains the <BR># configuration directives that give the server its instructions. <BR># See <URL:http://www.apache.org/docs/> for detailed information about <BR># the directives. <BR># <BR># Do NOT simply read the instructions in here without understanding <BR># what they do. They're here only as hints or reminders. If you are unsure <BR># consult the online docs. You have been warned. <BR># <BR># After this file is processed, the server will look for and process <BR># D:/usr/local/apache/Apache/conf/srm.conf and then D:/usr/local/apache/Apache/conf/access.conf <BR># unless you have overridden these with ResourceConfig and/or <BR># AccessConfig directives here. <BR># <BR># The configuration directives are grouped into three basic sections: <BR># 1. Directives that control the operation of the Apache server process as a <BR># whole (the 'global environment'). <BR># 2. Directives that define the parameters of the 'main' or 'default' server, <BR># which responds to requests that aren't handled by a virtual host. <BR># These directives also provide default values for the settings <BR># of all virtual hosts. <BR># 3. Settings for virtual hosts, which allow Web requests to be sent to <BR># different IP addresses or hostnames and have them handled by the <BR># same Apache server process. <BR># <BR># Configuration and logfile names: If the filenames you specify for many <BR># of the server's control files begin with "/" (or "drive:/" for Win32), the <BR># server will use that explicit path. If the filenames do *not* begin <BR># with "/", the value of ServerRoot is prepended -- so "logs/foo.log" <BR># with ServerRoot set to "/usr/local/apache" will be interpreted by the <BR># server as "/usr/local/apache/logs/foo.log". <BR># <BR># NOTE: Where filenames are specified, you must use forward slashes <BR># instead of backslashes (e.g., "c:/apache" instead of "c:\apache"). <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># <BR> <BR>### Section 1: Global Environment <BR># <BR># The directives in this section affect the overall operation of Apache, <BR># such as the number of concurrent requests it can handle or where it <BR># can find its configuration files. <BR># <BR> <BR># <BR># ServerType is either inetd, or standalone. Inetd mode is only supported on <BR># Unix platforms. <BR># <BR>ServerType standalone <BR> <BR># <BR># ServerRoot: The top of the directory tree under which the server's <BR># configuration, error, and log files are kept. <BR># <BR>ServerRoot "D:/usr/local/apache/Apache" <BR> <BR># <BR># PidFile: The file in which the server should record its process <BR># identification number when it starts. <BR># <BR>PidFile logs/httpd.pid <BR> <BR># <BR># ScoreBoardFile: File used to store internal server process information. <BR># Not all architectures require this. But if yours does (you'll know because <BR># this file will be created when you run Apache) then you *must* ensure that <BR># no two invocations of Apache share the same scoreboard file. <BR># <BR>ScoreBoardFile logs/apache_runtime_status <BR> <BR># <BR># In the standard configuration, the server will process httpd.conf (this <BR># file, specified by the -f command line option), srm.conf, and access.conf <BR># in that order. The latter two files are now distributed empty, as it is <BR># recommended that all directives be kept in a single file for simplicity. <BR># The commented-out values below are the built-in defaults. You can have the <BR># server ignore these files altogether by using "/dev/null" (for Unix) or <BR># "nul" (for Win32) for the arguments to the directives. <BR># <BR>#ResourceConfig conf/srm.conf <BR>#AccessConfig conf/access.conf <BR> <BR># <BR># Timeout: The number of seconds before receives and sends time out. <BR># <BR>Timeout 300 <BR> <BR># <BR># KeepAlive: Whether or not to allow persistent connections (more than <BR># one request per connection). Set to "Off" to deactivate. <BR># <BR>KeepAlive On <BR> <BR># <BR># MaxKeepAliveRequests: The maximum number of requests to allow <BR># during a persistent connection. Set to 0 to allow an unlimited amount. <BR># We recommend you leave this number high, for maximum performance. <BR># <BR>MaxKeepAliveRequests 100 <BR> <BR># <BR># KeepAliveTimeout: Number of seconds to wait for the next request from the <BR># same client on the same connection. <BR># <BR>KeepAliveTimeout 15 <BR> <BR># <BR># Apache on Win32 always creates one child process to handle requests. If it <BR># dies, another child process is created automatically. Within the child <BR># process multiple threads handle incoming requests. The next two <BR># directives control the behaviour of the threads and processes. <BR># <BR> <BR># <BR># MaxRequestsPerChild: the number of requests each child process is <BR># allowed to process before the child dies. The child will exit so <BR># as to avoid problems after prolonged use when Apache (and maybe the <BR># libraries it uses) leak memory or other resources. On most systems, this <BR># isn't really needed, but a few (such as Solaris) do have notable leaks <BR># in the libraries. For Win32, set this value to zero (unlimited) <BR># unless advised otherwise. <BR># <BR># NOTE: This value does not include keepalive requests after the initial <BR># request per connection. For example, if a child process handles <BR># an initial request and 10 subsequent "keptalive" requests, it <BR># would only count as 1 request towards this limit. <BR># <BR>MaxRequestsPerChild 0 <BR> <BR># <BR># Number of concurrent threads (i.e., requests) the server will allow. <BR># Set this value according to the responsiveness of the server (more <BR># requests active at once means they're all handled more slowly) and <BR># the amount of system resources you'll allow the server to consume. <BR># <BR>ThreadsPerChild 50 <BR> <BR># <BR># Listen: Allows you to bind Apache to specific IP addresses and/or <BR># ports, in addition to the default. See also the <VirtualHost> <BR># directive. <BR># <BR>Listen 212.46.201.219:80 <BR>#Listen 12.34.56.78:80 <BR> <BR># <BR># BindAddress: You can support virtual hosts with this option. This directive <BR># is used to tell the server which IP address to listen to. It can either <BR># contain "*", an IP address, or a fully qualified Internet domain name. <BR># See also the <VirtualHost> and Listen directives. <BR># <BR>#BindAddress * <BR> <BR># <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' lines at this location so the <BR># directives contained in it are actually available _before_ they are used. <BR># Please read the file README.DSO in the Apache 1.3 distribution for more <BR># details about the DSO mechanism and run `apache -l' for the list of already <BR># built-in (statically linked and thus always available) modules in your Apache <BR># binary. <BR># <BR># Note: The order in which modules are loaded is important. Don't change <BR># the order below without expert advice. <BR># <BR># Example: <BR># LoadModule foo_module modules/mod_foo.so <BR># <BR>#LoadModule vhost_alias_module modules/mod_vhost_alias.so <BR>#LoadModule mime_magic_module modules/mod_mime_magic.so <BR>#LoadModule status_module modules/mod_status.so <BR>#LoadModule info_module modules/mod_info.so <BR>#LoadModule speling_module modules/mod_speling.so <BR>#LoadModule rewrite_module modules/mod_rewrite.so <BR>#LoadModule anon_auth_module modules/mod_auth_anon.so <BR>#LoadModule dbm_auth_module modules/mod_auth_dbm.so <BR>#LoadModule digest_auth_module modules/mod_auth_digest.so <BR>#LoadModule digest_module modules/mod_digest.so <BR>#LoadModule proxy_module modules/mod_proxy.so <BR>#LoadModule cern_meta_module modules/mod_cern_meta.so <BR>#LoadModule expires_module modules/mod_expires.so <BR>#LoadModule headers_module modules/mod_headers.so <BR>#LoadModule usertrack_module modules/mod_usertrack.so <BR>#LoadModule unique_id_module modules/mod_unique_id.so <BR> <BR># <BR># Reconstruction of the complete module list from all available modules <BR># (static and shared ones) to achieve correct module execution order. <BR># <BR># The modules listed below, without a corresponding LoadModule directive, <BR># are static bound into the standard Apache binary distribution for Windows. <BR># <BR># Note: The order in which modules are loaded is important. Don't change <BR># the order below without expert advice. <BR># <BR># [WHENEVER YOU CHANGE THE LOADMODULE SECTION ABOVE, UPDATE THIS TOO!] <BR>ClearModuleList <BR>#AddModule mod_vhost_alias.c <BR>AddModule mod_env.c <BR>AddModule mod_log_config.c <BR>#AddModule mod_mime_magic.c <BR>AddModule mod_mime.c <BR>AddModule mod_negotiation.c <BR>#AddModule mod_status.c <BR>#AddModule mod_info.c <BR>AddModule mod_include.c <BR>AddModule mod_autoindex.c <BR>AddModule mod_dir.c <BR>AddModule mod_isapi.c <BR>AddModule mod_cgi.c <BR>AddModule mod_asis.c <BR>AddModule mod_imap.c <BR>AddModule mod_actions.c <BR>#AddModule mod_speling.c <BR>AddModule mod_userdir.c <BR>AddModule mod_alias.c <BR>#AddModule mod_rewrite.c <BR>AddModule mod_access.c <BR>AddModule mod_auth.c <BR>#AddModule mod_auth_anon.c <BR>#AddModule mod_auth_dbm.c <BR>#AddModule mod_auth_digest.c <BR>#AddModule mod_digest.c <BR>#AddModule mod_proxy.c <BR>#AddModule mod_cern_meta.c <BR>#AddModule mod_expires.c <BR>#AddModule mod_headers.c <BR>#AddModule mod_usertrack.c <BR>#AddModule mod_unique_id.c <BR>AddModule mod_so.c <BR>AddModule mod_setenvif.c <BR> <BR> <BR># <BR># ExtendedStatus controls whether Apache will generate "full" status <BR># information (ExtendedStatus On) or just basic information (ExtendedStatus <BR># Off) when the "server-status" handler is called. The default is Off. <BR># <BR>#ExtendedStatus On <BR> <BR>### Section 2: 'Main' server configuration <BR># <BR># The directives in this section set up the values used by the 'main' <BR># server, which responds to any requests that aren't handled by a <BR># <VirtualHost> definition. These values also provide defaults for <BR># any <VirtualHost> containers you may define later in the file. <BR># <BR># All of these directives may appear inside <VirtualHost> containers, <BR># in which case these default settings will be overridden for the <BR># virtual host being defined. <BR># <BR> <BR># <BR># Port: The port to which the standalone server listens. Certain firewall <BR># products must be configured before Apache can listen to a specific port. <BR># Other running httpd servers will also interfere with this port. Disable <BR># all firewall, security, and other services if you encounter problems. <BR># To help diagnose problems use the Windows NT command NETSTAT -a <BR># <BR>Port 80 <BR> <BR># <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. <BR># <BR>ServerAdmin <!-- BBcode auto-mailto start --><a href="mailto:webmaster@mysite.ru">webmaster@mysite.ru</a><!-- BBCode auto-mailto end --> <BR> <BR># <BR># ServerName allows you to set a host name which is sent back to clients for <BR># your server if it's different than the one the program would get (i.e., use <BR># "www" instead of the host's real name). <BR># <BR># Note: You cannot just invent host names and hope they work. The name you <BR># define here must be a valid DNS name for your host. If you don't understand <BR># this, ask your network administrator. <BR># If your host doesn't have a registered DNS name, enter its IP address here. <BR># You will have to access it by its address (e.g., <!-- BBCode auto-link start --><a href="http://123.45.67.89/)" target="_blank">http://123.45.67.89/)</a><!-- BBCode auto-link end --> <BR># anyway, and this will make redirections work in a sensible way. <BR># <BR># 127.0.0.1 is the TCP/IP local loop-back address, often named localhost. Your <BR># machine always knows itself by this address. If you use Apache strictly for <BR># local testing and development, you may use 127.0.0.1 as the server name. <BR># <BR>ServerName <!-- BBCode auto-link start --><a href="http://212.46.201.219/" target="_blank">http://212.46.201.219/</a><!-- BBCode auto-link end --> <BR> <BR> <BR># <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 "D:/usr/local/apache/Apache/htdocs" <BR> <BR># <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 "default" to be a very restrictive set of <BR># permissions. <BR># <BR><Directory /> <BR> Options FollowSymLinks <BR> AllowOverride All <BR></Directory> <BR> <BR># <BR># Note that from this point forward you must specifically allow <BR># particular features to be enabled - so if something's not working as <BR># you might expect, make sure that you have specifically enabled it <BR># below. <BR># <BR> <BR># <BR># This should be changed to whatever you set DocumentRoot to. <BR># <BR><Directory "D:/usr/local/apache/Apache/htdocs"> <BR> <BR># <BR># This may also be "None", "All", or any combination of "Indexes", <BR># "Includes", "FollowSymLinks", "ExecCGI", or "MultiViews". <BR># <BR># Note that "MultiViews" must be named *explicitly* --- "Options All" <BR># doesn't give it to you. <BR># <BR> Options Indexes FollowSymLinks MultiViews <BR> <BR># <BR># This controls which options the .htaccess files in directories can <BR># override. Can also be "All", or any combination of "Options", "FileInfo", <BR># "AuthConfig", and "Limit" <BR># <BR> AllowOverride All <BR> <BR># <BR># Controls who can get stuff from this server. <BR># <BR> Order allow,deny <BR> Allow from all <BR></Directory> <BR> <BR># <BR># UserDir: The name of the directory which is appended onto a user's home <BR># directory if a ~user request is received. <BR># <BR># Under Win32, we do not currently try to determine the home directory of <BR># a Windows login, so a format such as that below needs to be used. See <BR># the UserDir documentation for details. <BR># <BR><IfModule mod_userdir.c> <BR> UserDir "D:/usr/local/apache/Apache/users/" <BR></IfModule> <BR> <BR># <BR># Control access to UserDir directories. The following is an example <BR># for a site where these directories are restricted to read-only. <BR># <BR>#<Directory "D:/usr/local/apache/Apache/users"> <BR># AllowOverride FileInfo AuthConfig Limit <BR># Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec <BR># <Limit GET POST OPTIONS PROPFIND> <BR># Order allow,deny <BR># Allow from all <BR># </Limit> <BR># <LimitExcept GET POST OPTIONS PROPFIND> <BR># Order deny,allow <BR># Deny from all <BR># </LimitExcept> <BR>#</Directory> <BR> <BR># <BR># DirectoryIndex: Name of the file or files to use as a pre-written HTML <BR># directory index. Separate multiple entries with spaces. <BR># <BR><IfModule mod_dir.c> <BR> DirectoryIndex index.html <BR></IfModule> <BR> <BR># <BR># AccessFileName: The name of the file to look for in each directory <BR># for access control information. <BR># <BR>AccessFileName .htaccess <BR> <BR># <BR># The following lines prevent .htaccess files from being viewed by <BR># Web clients. Since .htaccess files often contain authorization <BR># information, access is disallowed for security reasons. Comment <BR># these lines out if you want Web visitors to see the contents of <BR># .htaccess files. If you change the AccessFileName directive above, <BR># be sure to make the corresponding changes here. <BR># <BR># Also, folks tend to use names such as .htpasswd for password <BR># files, so this will protect those as well. <BR># <BR><Files ~ "^\.ht"> <BR> Order allow,deny <BR> Deny from all <BR> Satisfy All <BR></Files> <BR> <BR># <BR># CacheNegotiatedDocs: By default, Apache sends "Pragma: no-cache" with each <BR># document that was negotiated on the basis of content. This asks proxy <BR># servers not to cache the document. Uncommenting the following line disables <BR># this behavior, and proxies will be allowed to cache the documents. <BR># <BR>#CacheNegotiatedDocs <BR> <BR># <BR># UseCanonicalName: (new for 1.3) With this setting turned on, whenever <BR># Apache needs to construct a self-referencing URL (/zoonews/a URL that refers back <BR># to the server the response is coming from) it will use ServerName and <BR># Port to form a "canonical" name. With this setting off, Apache will <BR># use the hostname:port that the client supplied, when possible. This <BR># also affects SERVER_NAME and SERVER_PORT in CGI scripts. <BR># <BR>UseCanonicalName Off <BR> <BR># <BR># TypesConfig describes where the mime.types file (or equivalent) is <BR># to be found. <BR># <BR><IfModule mod_mime.c> <BR> TypesConfig conf/mime.types <BR></IfModule> <BR> <BR># <BR># DefaultType is 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, "text/plain" is <BR># a good value. If most of your content is binary, such as applications <BR># or images, you may want to use "application/octet-stream" instead to <BR># keep browsers from trying to display binary files as though they are <BR># text. <BR># <BR>DefaultType text/plain <BR> <BR># <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># mod_mime_magic is not part of the default server (you have to add <BR># it yourself with a LoadModule [see the DSO paragraph in the 'Global <BR># Environment' section], or recompile the server and include mod_mime_magic <BR># as part of the configuration), so it's enclosed in an <IfModule> container. <BR># This means that the MIMEMagicFile directive will only be processed if the <BR># module is part of the server. <BR># <BR><IfModule mod_mime_magic.c> <BR> MIMEMagicFile conf/magic <BR></IfModule> <BR> <BR># <BR># HostnameLookups: Log the names of clients or just their IP addresses <BR># e.g., <!-- BBCode auto-link start --><a href="http://www.apache.org" target="_blank">www.apache.org</a><!-- BBCode auto-link end --> (on) or 204.62.129.132 (off). <BR># The default is off because it'd be overall better for the net if people <BR># had to knowingly turn this feature on, since enabling it means that <BR># each client request will result in AT LEAST one lookup request to the <BR># nameserver. <BR># <BR>HostnameLookups On <BR> <BR># <BR># ErrorLog: The location of the error log file. <BR># If you do not specify an ErrorLog directive within a <VirtualHost> <BR># container, error messages relating to that virtual host will be <BR># logged here. If you *do* define an error logfile for a <VirtualHost> <BR># container, that host's errors will be logged there and not here. <BR># <BR>ErrorLog logs/error.log <BR> <BR># <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 <BR> <BR># <BR># The following directives define some format nicknames for use with <BR># a CustomLog directive (see below). <BR># <BR>LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined <BR>LogFormat "%h %l %u %t \"%r\" %>s %b" common <BR>LogFormat "%{Referer}i -> %U" referer <BR>LogFormat "%{User-agent}i" agent <BR> <BR># <BR># The location and format of the access logfile (Common Logfile Format). <BR># If you do not define any access logfiles within a <VirtualHost> <BR># container, they will be logged here. Contrariwise, if you *do* <BR># define per-<VirtualHost> access logfiles, transactions will be <BR># logged therein and *not* in this file. <BR># <BR>CustomLog logs/access.log common <BR> <BR># <BR># If you would like to have agent and referer logfiles, uncomment the <BR># following directives. <BR># <BR>#CustomLog logs/referer.log referer <BR>#CustomLog logs/agent.log agent <BR> <BR># <BR># If you prefer a single 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> <BR># <BR># Optionally add a line containing the server version and virtual host <BR># name to server-generated pages (error documents, FTP directory listings, <BR># mod_status and mod_info output etc., but not CGI generated documents). <BR># Set to "EMail" to also include a mailto: link to the ServerAdmin. <BR># Set to one of: On | Off | EMail <BR># <BR>ServerSignature On <BR> <BR># <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: <BR> <BR> #!c:/program files/perl/perl <BR> <BR># 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># 'Folder Options', and reviewing the 'File Types' tab. Clicking the Edit <BR># button allows you to modify the Actions, of which Apache 1.3 attempts to <BR># perform the 'Open' 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's own specific security weaknesses, from the means <BR># to run a program you didn'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 <Directory> blocks or the <BR># .htaccess file, with either the 'registry' (Windows behavior) or 'script' <BR># (Unix behavior) option, and will override this server default option. <BR># <BR> <BR># <BR># Aliases: Add here as many aliases as you need (with no limit). The format is <BR># Alias fakename realname <BR># <BR><IfModule mod_alias.c> <BR> <BR> # <BR> # Note that if you include a trailing / on fakename then the server will <BR> # require it to be present in the URL. So "/icons" isn't aliased in this <BR> # example, only "/icons/". If the fakename is slash-terminated, then the <BR> # realname must also be slash terminated, and if the fakename omits the <BR> # trailing slash, the realname must also omit it. <BR> # <BR> Alias /icons/ "D:/usr/local/apache/Apache/icons/" <BR> <BR> <Directory "D:/usr/local/apache/Apache/icons"> <BR> Options Indexes MultiViews <BR> AllowOverride All <BR> Order allow,deny <BR> Allow from all <BR> </Directory> <BR> <BR> # This Alias will project the on-line documentation tree under /manual/ <BR> # even if you change the DocumentRoot. Comment it if you don't want to <BR> # provide access to the on-line documentation. <BR> # <BR> Alias /manual/ "D:/usr/local/apache/Apache/htdocs/manual/" <BR> <BR> <Directory "D:/usr/local/apache/Apache/htdocs/manual"> <BR> Options Indexes FollowSymlinks MultiViews <BR> AllowOverride All <BR> Order allow,deny <BR> Allow from all <BR> </Directory> <BR> <BR> # <BR> # ScriptAlias: This controls which directories contain server scripts. <BR> # ScriptAliases are essentially the same as Aliases, except that <BR> # documents in the realname directory are treated as applications and <BR> # run by the server when requested rather than as documents sent to the client. <BR> # The same rules about trailing "/" apply to ScriptAlias directives as to <BR> # Alias. <BR> # <BR> ScriptAlias /cgi-bin/ "D:/usr/local/apache/Apache/cgi-bin/" <BR> <BR> # <BR> # "D:/usr/local/apache/Apache/cgi-bin" should be changed to whatever your ScriptAliased <BR> # CGI directory exists, if you have that configured. <BR> # <BR> <Directory "D:/usr/local/apache/Apache/cgi-bin"> <BR> AllowOverride None <BR> Options None <BR> Order allow,deny <BR> Allow from all <BR> </Directory> <BR> <BR></IfModule> <BR># End of aliases. <BR> <BR># <BR># Redirect allows you to tell clients about documents which used to exist in <BR># your server's namespace, but do not anymore. This allows you to tell the <BR># clients where to look for the relocated document. <BR># Format: Redirect old-URI new-URL <BR># <BR> <BR># <BR># Directives controlling the display of server-generated directory listings. <BR># <BR><IfModule mod_autoindex.c> <BR> <BR> # <BR> # FancyIndexing is whether you want fancy directory indexing or standard <BR> # <BR> # Note, add the option TrackModified to the IndexOptions default list only <BR> # if all indexed directories reside on NTFS volumes. The TrackModified flag <BR> # will report the Last-Modified date to assist caches and proxies to properly <BR> # track directory changes, but it does _not_ work on FAT volumes. <BR> # <BR> IndexOptions FancyIndexing <BR> <BR> # <BR> # AddIcon* directives tell the server which icon to show for different <BR> # files or filename extensions. These are only displayed for <BR> # FancyIndexed directories. <BR> # <BR> AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip <BR> <BR> AddIconByType (TXT,/icons/text.gif) text/* <BR> AddIconByType (IMG,/icons/image2.gif) image/* <BR> AddIconByType (SND,/icons/sound2.gif) audio/* <BR> AddIconByType (VID,/icons/movie.gif) video/* <BR> <BR> AddIcon /icons/binary.gif .bin .exe <BR> AddIcon /icons/binhex.gif .hqx <BR> AddIcon /icons/tar.gif .tar <BR> AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv <BR> AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip <BR> AddIcon /icons/a.gif .ps .ai .eps <BR> AddIcon /icons/layout.gif .html .shtml .htm .pdf <BR> AddIcon /icons/text.gif .txt <BR> AddIcon /icons/c.gif .c <BR> AddIcon /icons/p.gif .pl .py <BR> AddIcon /icons/f.gif .for <BR> AddIcon /icons/dvi.gif .dvi <BR> AddIcon /icons/uuencoded.gif .uu <BR> AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl <BR> AddIcon /icons/tex.gif .tex <BR> AddIcon /icons/bomb.gif core <BR> <BR> AddIcon /icons/back.gif .. <BR> AddIcon /icons/hand.right.gif README <BR> AddIcon /icons/folder.gif ^^DIRECTORY^^ <BR> AddIcon /icons/blank.gif ^^BLANKICON^^ <BR> <BR> # <BR> # DefaultIcon is which icon to show for files which do not have an icon <BR> # explicitly set. <BR> # <BR> DefaultIcon /icons/unknown.gif <BR> <BR> # <BR> # AddDescription allows you to place a short description after a file in <BR> # server-generated indexes. These are only displayed for FancyIndexed <BR> # directories. <BR> # Format: AddDescription "description" filename <BR> # <BR> #AddDescription "GZIP compressed document" .gz <BR> #AddDescription "tar archive" .tar <BR> #AddDescription "GZIP compressed tar archive" .tgz <BR> <BR> # <BR> # ReadmeName is the name of the README file the server will look for by <BR> # default, and append to directory listings. <BR> # <BR> # HeaderName is the name of a file which should be prepended to <BR> # directory indexes. <BR> # <BR> # If MultiViews are amongst the Options in effect, the server will <BR> # first look for name.html and include it if found. If name.html <BR> # doesn't exist, the server will then look for name.txt and include <BR> # it as plaintext if found. <BR> # <BR> ReadmeName README <BR> HeaderName HEADER <BR> <BR> # <BR> # IndexIgnore is a set of filenames which directory indexing should ignore <BR> # and not include in the listing. Shell-style wildcarding is permitted. <BR> # <BR> IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t <BR> <BR></IfModule> <BR># End of indexing directives. <BR> <BR># <BR># Document types. <BR># <BR><IfModule mod_mime.c> <BR> <BR> # <BR> # AddEncoding allows you to have certain browsers (Mosaic/X 2.1+) uncompress <BR> # information on the fly. Note: Not all browsers support this. <BR> # Despite the name similarity, the following Add* directives have nothing <BR> # to do with the FancyIndexing customization directives above. <BR> # <BR> AddEncoding x-compress Z <BR> AddEncoding x-gzip gz tgz <BR> # <BR> # AddLanguage allows you to specify the language of a document. You can <BR> # then use content negotiation to give a browser a file in a language <BR> # it can understand. <BR> # <BR> # Note 1: The suffix does not have to be the same as the language <BR> # keyword --- those with documents in Polish (whose net-standard <BR> # language code is pl) may wish to use "AddLanguage pl .po" to <BR> # avoid the ambiguity with the common suffix for perl scripts. <BR> # <BR> # Note 2: The example entries below illustrate that in quite <BR> # some cases the two character 'Language' abbreviation is not <BR> # identical to the two character 'Country' code for its country, <BR> # E.g. 'Danmark/dk' versus 'Danish/da'. <BR> # <BR> # Note 3: In the case of 'ltz' we violate the RFC by using a three char <BR> # specifier. But there is 'work in progress' to fix this and get <BR> # the reference data for rfc1766 cleaned up. <BR> # <BR> # Danish (da) - Dutch (nl) - English (en) - Estonian (ee) <BR> # French (fr) - German (de) - Greek-Modern (el) <BR> # Italian (it) - Korean (kr) - Norwegian (no) - Norwegian Nynorsk (nn) <BR> # Portugese (pt) - Luxembourgeois* (ltz) <BR> # Spanish (es) - Swedish (sv) - Catalan (ca) - Czech(cz) <BR> # Polish (pl) - Brazilian Portuguese (pt-br) - Japanese (ja) <BR> # Russian (ru) <BR> # <BR> AddLanguage da .dk <BR> AddLanguage nl .nl <BR> AddLanguage en .en <BR> AddLanguage et .ee <BR> AddLanguage fr .fr <BR> AddLanguage de .de <BR> AddLanguage el .el <BR> AddLanguage he .he <BR> AddCharset ISO-8859-8 .iso8859-8 <BR> AddLanguage it .it <BR> AddLanguage ja .ja <BR> AddCharset ISO-2022-JP .jis <BR> AddLanguage kr .kr <BR> AddCharset ISO-2022-KR .iso-kr <BR> AddLanguage nn .nn <BR> AddLanguage no .no <BR> AddLanguage pl .po <BR> AddCharset ISO-8859-2 .iso-pl <BR> AddLanguage pt .pt <BR> AddLanguage pt-br .pt-br <BR> AddLanguage ltz .lu <BR> AddLanguage ca .ca <BR> AddLanguage es .es <BR> AddLanguage sv .sv <BR> AddLanguage cz .cz <BR> AddLanguage ru .ru <BR> AddLanguage tw .tw <BR> AddLanguage zh-tw .tw <BR> AddCharset Big5 .Big5 .big5 <BR> AddCharset WINDOWS-1251 .cp-1251 <BR> AddCharset CP866 .cp866 <BR> AddCharset ISO-8859-5 .iso-ru <BR> AddCharset KOI8-R .koi8-r <BR> AddCharset UCS-2 .ucs2 <BR> AddCharset UCS-4 .ucs4 <BR> AddCharset UTF-8 .utf8 <BR> <BR> # LanguagePriority allows you to give precedence to some languages <BR> # in case of a tie during content negotiation. <BR> # <BR> # Just list the languages in decreasing order of preference. We have <BR> # more or less alphabetized them here. You probably want to change this. <BR> # <BR> <IfModule mod_negotiation.c> <BR> LanguagePriority en da nl et fr de el it ja kr no pl pt pt-br ru ltz ca es sv tw <BR> </IfModule> <BR> <BR> # <BR> # AddType allows you to tweak mime.types without actually editing it, or to <BR> # make certain files to be certain types. <BR> # <BR> AddType application/x-tar .tgz <BR> <BR> # <BR> # AddHandler allows you to map certain file extensions to "handlers", <BR> # actions unrelated to filetype. These can be either built into the server <BR> # or added with the Action command (see below) <BR> # <BR> # If you want to use server side includes, or CGI outside <BR> # ScriptAliased directories, uncomment the following lines. <BR> # <BR> # To use CGI scripts: <BR> # <BR> #AddHandler cgi-script .cgi <BR> <BR> # <BR> # To use server-parsed HTML files <BR> # <BR> #AddType text/html .shtml <BR> #AddHandler server-parsed .shtml <BR> <BR> # <BR> # Uncomment the following line to enable Apache's send-asis HTTP file <BR> # feature <BR> # <BR> #AddHandler send-as-is asis <BR> <BR> # <BR> # If you wish to use server-parsed imagemap files, use <BR> # <BR> #AddHandler imap-file map <BR> <BR> # <BR> # To enable type maps, you might want to use <BR> # <BR> #AddHandler type-map var <BR> <BR></IfModule> <BR># End of document types. <BR> <BR># <BR># Action lets you define media types that will execute a script whenever <BR># a matching file is called. This eliminates the need for repeated URL <BR># pathnames for oft-used CGI file processors. <BR># Format: Action media/type /cgi-script/location <BR># Format: Action handler-name /cgi-script/location <BR># <BR> <BR># <BR># MetaDir: specifies the name of the directory in which Apache can find <BR># meta information files. These files contain additional HTTP headers <BR># to include when sending the document <BR># <BR>#MetaDir .web <BR> <BR># <BR># MetaSuffix: specifies the file name suffix for the file containing the <BR># meta information. <BR># <BR>#MetaSuffix .meta <BR> <BR># <BR># Customizable error response (Apache style) <BR># these come in three flavors <BR># <BR># 1) plain text <BR>#ErrorDocument 500 "The server made a boo boo. <BR># n.b. the single leading (") marks it as text, it does not get output <BR># <BR># 2) local redirects <BR>#ErrorDocument 404 /missing.html <BR># to redirect to local URL /missing.html <BR>#ErrorDocument 404 /cgi-bin/missing_handler.pl <BR># N.B.: You can redirect to a script or a document using server-side-includes. <BR># <BR># 3) external redirects <BR>#ErrorDocument 402 <!-- BBCode auto-link start --><a href="http://some.other-server.com/subscription_info.html" target="_blank">http://some.other-server.com/subscription_info.html</a><!-- BBCode auto-link end --> <BR># N.B.: Many of the environment variables associated with the original <BR># request will *not* be available to such a script. <BR> <BR># <BR># Customize behaviour based on the browser <BR># <BR><IfModule mod_setenvif.c> <BR> <BR> # <BR> # The following directives modify normal HTTP response behavior. <BR> # The first directive disables keepalive for Netscape 2.x and browsers that <BR> # spoof it. There are known problems with these browser implementations. <BR> # The second directive is for Microsoft Internet Explorer 4.0b2 <BR> # which has a broken HTTP/1.1 implementation and does not properly <BR> # support keepalive when it is used on 301 or 302 (redirect) responses. <BR> # <BR> BrowserMatch "Mozilla/2" nokeepalive <BR> BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0 <BR> <BR> # <BR> # The following directive disables HTTP/1.1 responses to browsers which <BR> # are in violation of the HTTP/1.0 spec by not being able to grok a <BR> # basic 1.1 response. <BR> # <BR> BrowserMatch "RealPlayer 4\.0" force-response-1.0 <BR> BrowserMatch "Java/1\.0" force-response-1.0 <BR> BrowserMatch "JDK/1\.0" force-response-1.0 <BR> <BR></IfModule> <BR># End of browser customization directives <BR> <BR># <BR># Allow server status reports, with the URL of <!-- BBCode auto-link start --><a href="http://servername/server-status" target="_blank">http://servername/server-status</a><!-- BBCode auto-link end --> <BR># Change the "popa.dyndns.ws" to match your domain to enable. <BR># <BR>#<Location /server-status> <BR># SetHandler server-status <BR># Order deny,allow <BR># Deny from all <BR># Allow from popa.dyndns.ws <BR>#</Location> <BR> <BR># <BR># Allow remote server configuration reports, with the URL of <BR># <!-- BBCode auto-link start --><a href="http://servername/server-info" target="_blank">http://servername/server-info</a><!-- BBCode auto-link end --> (requires that mod_info.c be loaded). <BR># Change the "popa.dyndns.ws" to match your domain to enable. <BR># <BR>#<Location /server-info> <BR># SetHandler server-info <BR># Order deny,allow <BR># Deny from all <BR># Allow from popa.dyndns.ws <BR>#</Location> <BR> <BR># <BR># There have been reports of people trying to abuse an old bug from pre-1.1 <BR># days. This bug involved a CGI script distributed as a part of Apache. <BR># By uncommenting these lines you can redirect these attacks to a logging <BR># script on phf.apache.org. Or, you can record them yourself, using the script <BR># support/phf_abuse_log.cgi. <BR># <BR>#<Location /cgi-bin/phf*> <BR># Deny from all <BR># ErrorDocument 403 <!-- BBCode auto-link start --><a href="http://phf.apache.org/phf_abuse_log.cgi" target="_blank">http://phf.apache.org/phf_abuse_log.cgi</a><!-- BBCode auto-link end --> <BR>#</Location> <BR> <BR># <BR># Proxy Server directives. Uncomment the following lines to <BR># enable the proxy server: <BR># <BR>#<IfModule mod_proxy.c> <BR># ProxyRequests On <BR> <BR># <Directory proxy:*> <BR># Order deny,allow <BR># Deny from all <BR># Allow from popa.dyndns.ws <BR># </Directory> <BR> <BR> # <BR> # Enable/disable the handling of HTTP/1.1 "Via:" headers. <BR> # ("Full" adds the server version; "Block" removes all outgoing Via: headers) <BR> # Set to one of: Off | On | Full | Block <BR> # <BR># ProxyVia On <BR> <BR> # <BR> # To enable the cache as well, edit and uncomment the following lines: <BR> # (no cacheing without CacheRoot) <BR> # <BR># CacheRoot "D:/usr/local/apache/Apache/proxy" <BR># CacheSize 5 <BR># CacheGcInterval 4 <BR># CacheMaxExpire 24 <BR># CacheLastModifiedFactor 0.1 <BR># CacheDefaultExpire 1 <BR># NoCache a-domain.com another-domain.edu joes.garage-sale.com <BR> <BR>#</IfModule> <BR># End of proxy directives. <BR>NameVirtualHost 127.0.0.2 <BR> <BR><VirtualHost 127.0.0.2> <BR>ServerAdmin <!-- BBcode auto-mailto start --><a href="mailto:d@mysite.ru">d@mysite.ru</a><!-- BBCode auto-mailto end --> <BR>ServerName LimpBizkit <BR>DocumentRoot "d:/usr/local/apache/Apache/htdocs" <BR>ScriptAlias /cgi/ "d:/usr/local/apache/Apache/cgi-bin/" <BR>ErrorLog d:/usr/local/apache/Apache/error.log <BR>CustomLog d:/usr/local/apache/Apache/access.log common <BR></VirtualHost> <BR> <BR> <BR> <BR> <BR>спасибо
Вернуться к началу
Посмотреть профиль Отправить личное сообщение Посетить сайт автора
Korn
Member


Зарегистрирован: 01.01.1970
Сообщения: 15

СообщениеДобавлено: 27.05.2002 03:40    Заголовок сообщения: Ответить с цитатой

бл... теги не пашут....
Вернуться к началу
Посмотреть профиль Отправить личное сообщение Посетить сайт автора
maxim
Member


Зарегистрирован: 01.01.1970
Сообщения: 9

СообщениеДобавлено: 01.06.2002 10:53    Заголовок сообщения: Ответить с цитатой

Ну и какого лешего ты сюда весь конф запостил? [censored. Пожалуйста, будет аккуратнее в высказываниях] <BR><BR><BR><font size=-1>[ Это Сообщение было отредактировано: KW в 2002-06-01 12:54 ]</font>
Вернуться к началу
Посмотреть профиль Отправить личное сообщение
Korn
Member


Зарегистрирован: 01.01.1970
Сообщения: 15

СообщениеДобавлено: 26.09.2002 00:24    Заголовок сообщения: Ответить с цитатой

спасибо я уже всё понял... <BR>[censored. Пожалуйста, будет аккуратнее в высказываниях] <BR><BR><BR><font size=-1>[ Это Сообщение было отредактировано: KW в 2002-09-26 16:18 ]</font>
Вернуться к началу
Посмотреть профиль Отправить личное сообщение Посетить сайт автора
Показать сообщения:   
Начать новую тему   Ответить на тему    Список форумов Net Форумы -> Apache настройки Часовой пояс: GMT + 3
Страница 1 из 1

 
Перейти:  
Вы не можете начинать темы
Вы не можете отвечать на сообщения
Вы не можете редактировать свои сообщения
Вы не можете удалять свои сообщения
Вы не можете голосовать в опросах


Powered by phpBB
Русская поддержка phpBB