Aktív témák
-
emitter
őstag
válasz VladimirR #80 üzenetére
ha rootként indítom az apache-ot, akkor meg foglalt socketet ír.. mi használhatja? A böngészőt ilyenkor zárjam be?? mod: bezártam, ugyanaz a hiba
httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
(98)Address already in use: make_sock: could not bind to address [::]:80
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
etc/init.d-ből indítva nem csinál semmit, visszaadja a promptot..
[Szerkesztve] -
emitter
őstag
válasz VladimirR #88 üzenetére
locate httpd.conf nem talál apache config-fájlt a drupal telepítő-mappájában.. (ott csak egy .htaccess van)
szóval még mindig nem értem, hogy van ez a dolog..
emitter@LAPTOP:~/drupal-5.0$ locate httpd.conf
/etc/apache/httpd.conf
/etc/apache2/httpd.conf
/usr/local/apache2/conf/original/httpd.conf
/usr/local/apache2/conf/httpd.conf
/usr/share/doc/apache/examples/httpd.conf
/usr/share/doc/apache-common/examples/httpd.conf-dist
/usr/share/apache/default-configs/apache-perl/httpd.conf
/usr/share/apache/default-configs/apache-ssl/httpd.conf
/usr/share/apache/default-configs/apache/httpd.conf
/home/emitter/Downloads/apache/httpd-2.2.4/docs/conf/httpd.conf
/home/emitter/Downloads/apache/httpd-2.2.4/docs/conf/httpd.conf.in -
-
r0by
addikt
válasz VladimirR #134 üzenetére
Forrás: apache faq
Why can't I use SSL with name-based/non-IP-based virtual hosts?
The reason is very technical, and a somewhat "chicken and egg" problem. The SSL protocol layer stays below the HTTP protocol layer and encapsulates HTTP. When an SSL connection (HTTPS) is established Apache/mod_ssl has to negotiate the SSL protocol parameters with the client. For this, mod_ssl has to consult the configuration of the virtual server (for instance it has to look for the cipher suite, the server certificate, etc.). But in order to go to the correct virtual server Apache has to know the Host HTTP header field. To do this, the HTTP request header has to be read. This cannot be done before the SSL handshake is finished, but the information is needed in order to complete the SSL handshake phase. Bingo!
Why is it not possible to use Name-Based Virtual Hosting to identify different SSL virtual hosts?
Name-Based Virtual Hosting is a very popular method of identifying different virtual hosts. It allows you to use the same IP address and the same port number for many different sites. When people move on to SSL, it seems natural to assume that the same method can be used to have lots of different SSL virtual hosts on the same server.
It comes as rather a shock to learn that it is impossible.
The reason is that the SSL protocol is a separate layer which encapsulates the HTTP protocol. So the SSL session is a separate transaction, that takes place before the HTTP session has begun. The server receives an SSL request on IP address X and port Y (usually 443). Since the SSL request does not contain any Host: field, the server has no way to decide which SSL virtual host to use. Usually, it will just use the first one it finds, which matches the port and IP address specified.
You can, of course, use Name-Based Virtual Hosting to identify many non-SSL virtual hosts (all on port 80, for example) and then have a single SSL virtual host (on port 443). But if you do this, you must make sure to put the non-SSL port number on the NameVirtualHost directive, e.g.
NameVirtualHost 192.168.1.1:80
Aktív témák
Állásajánlatok
Cég: Ozeki Kft
Város: Debrecen
Cég: Ozeki Kft
Város: Debrecen