Apache服务器有坏的解释传入查询根据不相关的域名托管在一个单一的IP地址



有一个带有LAMP堆栈的Ubuntu服务器。
在一个IP地址上托管了一些站点。
IP地址"white"访问服务器没有任何问题。Server表示端口转发的NAT。

的情况是:有一些域托管在一个单一的IP地址的服务器上,例如domain1,domain2domain3. 在对服务器进行不相关查询的行为中,例如对domain3domain3/123subdomain.domain3(目录123和子域都不存在)或者直接查询IP地址,服务器会将此查询转发到列表中的第一个域(domain1)。

我怎样才能改变它?我需要下一步行动:在不相关的查询,响应必须是从已被请求的域。另一种方式,如果没有这样的目录,服务器必须返回关于不存在请求站点或忽略这些请求的答案。

在当前实现了下一个方案:在服务器上已经创建了一个名为domain0的目录并为它启动了虚拟服务器,上传了错误403和404的自定义页面。如果对任何不存在的域名进行了不相关的查询,那么Apache服务器将把此查询转发到列表中的第一个目录domain0然后用户将得到带有错误代码的页面。

所以,我被迫向Stack Overflow社区询问我的问题,以帮助我解决这个问题。如何实现Apache服务器设置,以正确解释传入查询?

提前感谢!

Apache配置:

# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.4/ for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian specific
# hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.
# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
#   /etc/apache2/
#   |-- apache2.conf
#   |   `--  ports.conf
#   |-- mods-enabled
#   |   |-- *.load
#   |   `-- *.conf
#   |-- conf-enabled
#   |   `-- *.conf
#   `-- sites-enabled
#       `-- *.conf
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
#   together by including all remaining configuration files when starting up the
#   web server.
#
# * ports.conf is always included from the main configuration file. It is
#   supposed to determine listening ports for incoming connections which can be
#   customized anytime.
#
# * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
#   directories contain particular configuration snippets which manage modules,
#   global configuration fragments, or virtual host configurations,
#   respectively.
#
#   They are activated by symlinking available configuration files from their
#   respective *-available/ counterparts. These should be managed by using our
#   helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
#   their respective man pages for detailed information.
#
# * The binary is called apache2. Due to the use of environment variables, in
#   the default configuration, apache2 needs to be started/stopped with
#   /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
#   work with the default configuration.
ServerSignature Off
ServerTokens Prod
# Global configuration
#
#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE!  If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the Mutex documentation (available
# at <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
#ServerRoot "/etc/apache2"
#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
#Mutex file:${APACHE_LOCK_DIR} default
#
# The directory where shm and other runtime files will be stored.
#
DefaultRuntimeDir ${APACHE_RUN_DIR}
#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}
#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300
#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On
#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100
#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 5

# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}
#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog ${APACHE_LOG_DIR}/error.log
#
# LogLevel: Control the severity of messages logged to the error_log.
# Available values: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the log level for particular modules, e.g.
# "LogLevel info ssl:warn"
#
LogLevel warn
# Include module configuration:
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf
# Include list of ports to listen on
Include ports.conf

# Sets the default security model of the Apache2 HTTPD server. It does
# not allow access to the root filesystem outside of /usr/share and /var/www.
# The former is used by web applications packaged in Debian,
# the latter may be used for local directories served by the web server. If
# your system is serving content from a sub-directory in /srv you must allow
# access here, or in any related virtual host.
<Directory />
Options FollowSymLinks
AllowOverride none
Require all denied
</Directory>
<Directory /usr/share>
AllowOverride None
Require all granted
</Directory>
<Directory /var/www/>
Options -Indexes
AllowOverride All
Require all granted
</Directory>
#<Directory /srv/>
#   Options Indexes FollowSymLinks
#   AllowOverride None
#   Require all granted
#</Directory>

# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives.  See also the AllowOverride
# directive.
#
AccessFileName .htaccess
#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^.ht">
Require all denied
</FilesMatch>

#
# The following directives define some format nicknames for use with
# a CustomLog directive.
#
# These deviate from the Common Log Format definitions in that they use %O
# (the actual bytes sent including headers) instead of %b (the size of the
# requested file), because the latter makes it impossible to detect partial
# requests.
#
# Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.
# Use mod_remoteip instead.
#
LogFormat "%v:%p %h %l %u %t "%r" %>s %O "%{Referer}i" "%{User-Agent}i"" vhost_combined
LogFormat "%h %l %u %t "%r" %>s %O "%{Referer}i" "%{User-Agent}i"" combined
LogFormat "%h %l %u %t "%r" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent
# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.
# Include generic snippets of statements
IncludeOptional conf-enabled/*.conf
# Include the virtual host configurations:
IncludeOptional sites-enabled/*.conf
# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

虚拟主机配置(所有VH相同):

<VirtualHost *:80>
# The ServerName directive sets the request scheme, hostname and port that
# the server uses to identify itself. This is used when creating
# redirection URLs. In the context of virtual hosts, the ServerName
# specifies what hostname must appear in the request's Host: header to
# match this virtual host. For the default virtual host (this file) this
# value is not decisive as it is used as a last resort host regardless.
# However, you must set it for any further virtual host explicitly.
ServerName domen3.name
ServerAlias www.domen3.name
ServerAdmin webmaster@localhost
DocumentRoot /var/www/domen3.name
# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the loglevel for particular
# modules, e.g.
#LogLevel info ssl:warn
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
# For most configuration files from conf-available/, which are
# enabled or disabled at a global level, it is possible to
# include a line for only one particular virtual host. For example the
# following line enables the CGI configuration for this host only
# after it has been globally disabled with "a2disconf".
#Include conf-available/serve-cgi-bin.conf
RewriteEngine on
RewriteCond %{SERVER_NAME} =domen3.name
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
</VirtualHost>
# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
<VirtualHost *:443>
Protocols h2 http/1.1
<IfModule mod_headers.c>
Header always set Strict-Transport-Security "max-age=63072000; includeSubDomains; preload"
</IfModule>
<IfModule mod_ssl.c>
# The ServerName directive sets the request scheme, hostname and port that
# the server uses to identify itself. This is used when creating
# redirection URLs. In the context of virtual hosts, the ServerName
# specifies what hostname must appear in the request's Host: header to
# match this virtual host. For the default virtual host (this file) this
# value is not decisive as it is used as a last resort host regardless.
# However, you must set it for any further virtual host explicitly.
ServerName domen3.name
ServerAlias www.domen3.name
ServerAdmin webmaster@localhost
DocumentRoot /var/www/domen3.name
# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the loglevel for particular
# modules, e.g.
#LogLevel info ssl:warn
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
# For most configuration files from conf-available/, which are
# enabled or disabled at a global level, it is possible to
# include a line for only one particular virtual host. For example the
# following line enables the CGI configuration for this host only
# after it has been globally disabled with "a2disconf".
#Include conf-available/serve-cgi-bin.conf
SSLCertificateFile /etc/letsencrypt/live/domen3.name/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/domen3.name/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf
</IfModule>
</VirtualHost>

你有多种可能的情况(因为你的问题对我来说不是很清楚)。

假设

  • 你的服务器响应IP 1.1.1.1
  • 使用Apache 2.4或更高版本

场景1

仅对http(端口80)流量:

Listen 80
<VirtualHost *:80>
ServerName www.example1.com
# REST OF CONFIG
</VirtualHost>
<VirtualHost *:80>
ServerName www.example2.com
# REST OF CONFIG
</VirtualHost>
<VirtualHost *:80>
ServerName www.example3.com
# REST OF CONFIG
</VirtualHost>

在这里,如果您请求http://www.example1.com,它将使用第一个。http://www.example2.com,它将使用第二个,等等。

如果您请求http://1.1.1.1/, Apache没有名称可供选择VirtualHost,所以它将使用第一个,因为它是默认的。这是没有办法的。你没有告诉Apache你想要哪个域,所以它是默认的。

如果您要求http://www.example4.com,假设www.example4.com == 1.1.1.1,Apache将再次使用第一个,因为它无法匹配任何其他

如果您请求http://www.example3.com/some_directory_error,您将收到来自第三个虚拟主机的404消息。无论你要什么域,都用某些非法路径,将由该域的VirtualHost响应。的只有在选择了VirtualHost后才检查请求的有效性


场景2

让我们假设它适用于端口80。现在对于端口443…

Listen 443
<VirtualHost *:443>
ServerName www.example1.com
# REST OF CONFIG
# SSL for example1
</VirtualHost>
<VirtualHost *:443>
ServerName www.example2.com
# REST OF CONFIG
# SSL for example2
</VirtualHost>
<VirtualHost *:443>
ServerName www.example3.com
# REST OF CONFIG
# SSL for example3
</VirtualHost>

这里,不管你的请求是什么(即https://www.example1.com,https://www.example2.com, https://1.1.1.1/, https://www.example4.com) Apache总是使用第一个吗?这是一个SSL限制。

原因是Apache只知道请求者想要的IP地址,但是不域名。对于SSL, Apache必须首先与浏览器协商对于密码、加密和证书。然后它将知道哪个VirtualHost使用。因此,对于证书协商,端口443的第一个VirtualHost是总是使用!

方法如下:

  • 每个域1个IP地址。所以在服务器上需要3个IP地址。
  • 每个域1个端口。你有一些网络设备从
  • 用户请求的域名:443,转到配置中指定的服务器端口。
  • SNI使用。对那个问题做些研究。前女友https://www.digicert.com/kb/ssl-support/apache-multiple-ssl-certificates-using-sni.htm

结论

你可以设置一个默认的VirtualHost。这个是第一个,而且不是指定ServerName或ServerAlias。只有默认的DocumentRoot和default404配置。参见Apache默认的VirtualHost


提示

将日志文件拆分到每个域

# Modify to the desired level
LogLevel debug
Listen 80
<VirtualHost *:80>
ServerName www.example1.com
# REST OF CONFIG
CustomLog logs/example1_80_access.log common
ErrorLog logs/example1_80_error.log
</VirtualHost>
<VirtualHost *:80>
ServerName www.example2.com
# REST OF CONFIG
CustomLog logs/example2_80_access.log common
ErrorLog logs/example2_80_error.log
</VirtualHost>
<VirtualHost *:80>
ServerName www.example3.com
# REST OF CONFIG
CustomLog logs/example3_80_access.log common
ErrorLog logs/example3_80_error.log
</VirtualHost>

这样你就知道发生了什么,每个VirtualHost。你已经有了一个全局日志文件,所以任何不"属于"的日志文件到一个特定的VirtualHost将在那里结束(logs/error.log)。

相关内容

  • 没有找到相关文章

最新更新