Perguntas[apache-http-server](computer)

Não consigo criar um subdomínio funcional no Apache. Antes de postar aqui, pesquisei na internet, li muitas perguntas semelhantes em sites de pilha, perguntei ao chatgpt, li a documentação do Apache e tentei várias configurações diferentes. (E claro. Eu reinicio httpdsempre :)

Mas estou preso. Eu diria que tenho bastante experiência em Linux, mas sou iniciante em Apache. Além disso, muitos recursos online são escritos a partir da perspectiva baseada no Debian, que difere consideravelmente do RedHat.

Meu ambiente

Estou usando Manjarocomo meu sistema operacional host. Aí eu tenho Rocky9 minimalcom httpd, rodando no Virtual box. É uma instalação nova, portanto não há configurações incorretas do passado.

O que eu quero alcançar

Quero acessar duas páginas diferentes da minha máquina host.

• idd.phdeveria mostrar/var/www/html/index.html
• example.idd.phdeveria mostrar/var/www/example/index.html

No entanto, sempre obtenho o mesmo index.htmlpara ambos os subdomínios.

• idd.phretorna/var/www/example/index.html
• example.idd.phtambém retorna/var/www/example/index.html

Se eu mudar a ordem do meu VirtualHosts, receberei /var/www/html/index.htmlos dois subdomínios.

Minha configuração

idd.phé um domínio arbitrário e está configurado /etc/hostsno meu host Manjaro :

192.168.0.109 idd.ph
192.168.0.109 example.idd.ph

No Rocky eu criei um arquivo normal.confdentro/etc/httpd/conf.d

<VirtualHost *:80>
    ServerName example.localhost
    DocumentRoot /var/www/example
</VirtualHost>

<VirtualHost *:80>
    ServerName localhost
    DocumentRoot /var/www/html
</VirtualHost>

Esta é a estrutura de /var/wwwou Rocky :

.
├── cgi-bin
├── example
│   └── index.html
└── html
    └── index.html

Eu também editei /etc/hostsno Rocky assim:

127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
127.0.0.1   example.localhost

Agradeço antecipadamente.

Estou tentando atualizar o PHP php-fpmde 8.1 para 8.2.

Por engano, apaguei os arquivos dentro/etc/php/8.2/fpm/conf.d

Tentei reiniciar php8.2-fpmo servidor Apache2, reinstalar php-fpm, mas eles não foram gerados novamente.

Eu vi que eles eram links simbólicos de /etc/php/8.2/mods-available/, então tentei recriá-los manualmente.

Mostra phpinfo()os arquivos .ini conforme carregados:

Porém, estou tendo problemas com o site rodando no servidor (Drupal).

Se eu fizer isso, por exemplo, drush cre recebo:

[preflight] A classe "DOMDocument" não existe

A partir desta pergunta , parece que php-xmlnão está realmente carregado.

Portanto, entendo que fiz algo errado.

Alguma sugestão?

Tentando o encaminhamento de porta, mas o ISP diz que só pode funcionar com um ip estático

Eu estava tentando encaminhar a porta do meu servidor apache2 do meu dispositivo arch Linux, hospedei meu servidor no meu ipv4: 192.168.1.5 e na porta padrão 80. Quando tentei encaminhar a porta do meu servidor, não funcionou, digitei meu ip 192.168.1.5 e em "from port to port" digitei 80 80 respectivamente. Mas não funcionou, liguei para meu ISP para resolver o problema, ele disse que preciso comprar um ip estático para fazer o encaminhamento de porta funcionar perfeitamente, perguntei a eles que quero encaminhar a porta com meu IP dinâmico para fins de teste mas ele me disse que a rede deles funciona em natting, então só posso encaminhar a porta se tiver um ip estático. Eu só quero saber se isso é verdade? Eu realmente preciso de ip estático para o portforward, tanto quanto sei, também podemos fazê-lo em IP dinâmico, corrija-me se estiver errado.

Usando uma gota, Ubuntu 18.04.6 LTS (GNU/Linux 4.15.0-209-generic x86_64)e apache2: Server version: Apache/2.4.29 (Ubuntu) Server built: 2023-03-08T17:34:33.

Eu tenho myservice.comtrabalho, como posso adicionar myservice.com/app?

Eu tenho na var/www/html/página principal. Fiz o dir /var/www/html/appe coloquei os arquivos lá mas não abre, Not Foundacontece erro (porta 443).

Como saber apache2se há uma subpágina em ./app?

Eu editei o arquivo de configuração para sites-availableser:

<VirtualHost xxx.xx.xxx.xxx:80>
    ServerAdmin root@localhost
    ServerName myservice.com
    ServerAlias www.myservice.com
    DocumentRoot /var/www/html/dist
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
    RewriteEngine on
    RewriteCond %{SERVER_NAME} =myservice.com [OR]
    RewriteCond %{SERVER_NAME} =www.myservice.com
    RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
</VirtualHost>

<VirtualHost xxx.xx.xxx.xxx:80>
    ServerName myservice.com/app
    DocumentRoot /var/www/html/app/dist
    RewriteEngine on
    RewriteCond %{SERVER_NAME} =myservice.com/app [OR]
    RewriteCond %{SERVER_NAME} =www.myservice.com/app
    RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
</VirtualHost>

Eu também corri sudo chmod -R 755 /var/www/myservice.com/app.

Esta é apache2.confa parte do diretório:

<Directory />
        Options FollowSymLinks
        AllowOverride None
        Require all denied
</Directory>

<Directory /usr/share>
        AllowOverride None
        Require all granted
</Directory>

<Directory /var/www/>
        Options Indexes FollowSymLinks
        AllowOverride ALL
        Require all granted
</Directory>

Encontrei soluções na Web para esse problema de 2005 que não funcionam e encontrei as mesmas soluções anos depois, por exemplo. a partir de 2017, isso não vai funcionar...

Por favor, diga-me que outras informações posso fornecer que possam ajudar a resolver o problema.

Eu tenho esta versão do Apache instalada:

ApacheFriends XAMPP (Basispaket) versão 1.6.8

• Apache 2.2.9
• MySQL 5.0.67 (Community Server)
• PHP 5.2.6 + PHP 4.4.9 + PEAR
• OpenSSL 0.9.8i

O certificado SSL foi ativado, mas recebo este erro no navegador se tento acessar https://localhost:

localhost uses an unsupported protocol.
ERR_SSL_VERSION_OR_CIPHER_MISMATCH
Unsupported protocol
The client and server don't support a common SSL protocol version or cipher suite.

Log de erros do Apache:

[Fri Apr 07 13:58:23 2023] [warn] RSA server certificate CommonName (CN) **name_of_the site** does NOT match server name!?
[Fri Apr 07 13:58:24 2023] [warn] RSA server certificate CommonName (CN) **name_of_the site** does NOT match server name!?
[Fri Apr 07 13:58:24 2023] [notice] Child 9956: Child process is running
[Fri Apr 07 13:58:24 2023] [notice] Child 9956: Acquired the start mutex.
[Fri Apr 07 13:58:24 2023] [notice] Child 9956: Starting 250 worker threads.
[Fri Apr 07 13:58:24 2023] [notice] Child 9956: Starting thread to listen on port 80.
[Fri Apr 07 13:58:24 2023] [notice] Child 9956: Starting thread to listen on port 443.

Este é o arquivo httpd-ssl.conf:

#
# This is the Apache server configuration file providing SSL support.
# It contains the configuration directives to instruct the server how to
# serve pages over an https connection. For detailing information about these
# directives see <URL:http://httpd.apache.org/docs/2.2/mod/mod_ssl.html>
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned.
#

#
# Pseudo Random Number Generator (PRNG):
# Configure one or more sources to seed the PRNG of the SSL library.
# The seed data should be of good random quality.
# WARNING! On some platforms /dev/random blocks if not enough entropy
# is available. This means you then cannot use the /dev/random device
# because it would lead to very long connection times (as long as
# it requires to make more entropy available). But usually those
# platforms additionally provide a /dev/urandom device which doesn't
# block. So, if available, use this one instead. Read the mod_ssl User
# Manual for more details.
#
#SSLRandomSeed startup file:/dev/random  512
#SSLRandomSeed startup file:/dev/urandom 512
#SSLRandomSeed connect file:/dev/random  512
#SSLRandomSeed connect file:/dev/urandom 512


#
# When we also provide SSL we have to listen to the
# standard HTTP port (see above) and to the HTTPS port
#
# Note: Configurations that use IPv6 but not IPv4-mapped addresses need two
#       Listen directives: "Listen [::]:443" and "Listen 0.0.0.0:443"
#
Listen 443

##
##  SSL Global Context
##
##  All SSL configuration in this context applies both to
##  the main server and all SSL-enabled virtual hosts.
##

#
#   Some MIME-types for downloading Certificates and CRLs
#
AddType application/x-x509-ca-cert .crt
AddType application/x-pkcs7-crl    .crl

#   Pass Phrase Dialog:
#   Configure the pass phrase gathering process.
#   The filtering dialog program (`builtin' is a internal
#   terminal dialog) has to provide the pass phrase on stdout.
SSLPassPhraseDialog  builtin

#   Inter-Process Session Cache:
#   Configure the SSL Session Cache: First the mechanism
#   to use and second the expiring timeout (in seconds).
#SSLSessionCache        shmcb:logs/ssl_scache(512000)
SSLSessionCache         dbm:logs/ssl.scache
SSLSessionCacheTimeout  300

#   Semaphore:
#   Configure the path to the mutual exclusion semaphore the
#   SSL engine uses internally for inter-process synchronization.
SSLMutex  default

##
## SSL Virtual Host Context
##

<VirtualHost _default_:443>
    #   General setup for the virtual host
    DocumentRoot "C:/xampp/htdocs/name_of_the_site"

    ServerName localhost:443
    ServerAdmin admin@localhost

    ErrorLog logs/error.log
    <IfModule log_config_module>
        CustomLog logs/access.log combined
    </IfModule>

    #   SSL Engine Switch:
    #   Enable/Disable SSL for this virtual host.
    SSLEngine on

    #   SSL Cipher Suite:
    #   List the ciphers that the client is permitted to negotiate.
    #   See the mod_ssl documentation for a complete list.
  
SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
        #   Server Certificate:
    #   Point SSLCertificateFile at a PEM encoded certificate.  If
    #   the certificate is encrypted, then you will be prompted for a
    #   pass phrase.  Note that a kill -HUP will prompt again.  Keep
    #   in mind that if you have both an RSA and a DSA certificate you
    #   can configure both in parallel (to also allow the use of DSA
    #   ciphers, etc.)
    #SSLCertificateFile conf/ssl.crt/snakeoil-rsa.crt
    #SSLCertificateFile conf/ssl.crt/snakeoil-dsa.crt
    # @SSLCertificateFile conf/ssl.crt/server.crt
#Radu
SSLCertificateFile conf/ssl.crt/name_of_the_site.crt
    #   Server Private Key:
    #   If the key is not combined with the certificate, use this
    #   directive to point at the key file.  Keep in mind that if
    #   you've both a RSA and a DSA private key you can configure
    #   both in parallel (to also allow the use of DSA ciphers, etc.)
    #SSLCertificateKeyFile conf/ssl.key/snakeoil-rsa.key
    #SSLCertificateKeyFile conf/ssl.key/snakeoil-dsa.key
    # @SSLCertificateKeyFile conf/ssl.key/server.key
#Radu
SSLCertificateKeyFile conf/ssl/name_of_the_site.key

    #   Server Certificate Chain:
    #   Point SSLCertificateChainFile at a file containing the
    #   concatenation of PEM encoded CA certificates which form the
    #   certificate chain for the server certificate. Alternatively
    #   the referenced file can be the same as SSLCertificateFile
    #   when the CA certificates are directly appended to the server
    #   certificate for convinience.
    #SSLCertificateChainFile conf/ssl.crt/ca.crt
# Radu
SSLCertificateChainFile conf/ssl/name_of_the_site-chain.pem

    #   Certificate Authority (CA):
    #   Set the CA certificate verification path where to find CA
    #   certificates for client authentication or alternatively one
    #   huge file containing all of them (file must be PEM encoded)
    #   Note: Inside SSLCACertificatePath you need hash symlinks
    #         to point to the certificate files. Use the provided
    #         Makefile to update the hash symlinks after changes.
    #SSLCACertificatePath conf/ssl.crt
    #SSLCACertificateFile conf/ssl.crt/ca-bundle.crt

    #   Certificate Revocation Lists (CRL):
    #   Set the CA revocation path where to find CA CRLs for client
    #   authentication or alternatively one huge file containing all
    #   of them (file must be PEM encoded)
    #   Note: Inside SSLCARevocationPath you need hash symlinks
    #         to point to the certificate files. Use the provided
    #         Makefile to update the hash symlinks after changes.
    #SSLCARevocationPath conf/ssl.crl
    #SSLCARevocationFile conf/ssl.crl/ca-bundle.crl

    #   Client Authentication (Type):
    #   Client certificate verification type and depth.  Types are
    #   none, optional, require and optional_no_ca.  Depth is a
    #   number which specifies how deeply to verify the certificate
    #   issuer chain before deciding the certificate is not valid.
    #SSLVerifyClient require
    #SSLVerifyDepth  10

    #   Access Control:
    #   With SSLRequire you can do per-directory access control based
    #   on arbitrary complex boolean expressions containing server
    #   variable checks and other lookup directives.  The syntax is a
    #   mixture between C and Perl.  See the mod_ssl documentation
    #   for more details.
    <Location />
        #SSLRequire (    %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
        #            and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
        #            and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
        #            and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
        #            and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20       ) \
        #           or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
    </Location>

    #   SSL Engine Options:
    #   Set various options for the SSL engine.
    #   o FakeBasicAuth:
    #     Translate the client X.509 into a Basic Authorisation.  This means that
    #     the standard Auth/DBMAuth methods can be used for access control.  The
    #     user name is the `one line' version of the client's X.509 certificate.
    #     Note that no password is obtained from the user. Every entry in the user
    #     file needs this password: `xxj31ZMTZzkVA'.
    #   o ExportCertData:
    #     This exports two additional environment variables: SSL_CLIENT_CERT and
    #     SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
    #     server (always existing) and the client (only existing when client
    #     authentication is used). This can be used to import the certificates
    #     into CGI scripts.
    #   o StdEnvVars:
    #     This exports the standard SSL/TLS related `SSL_*' environment variables.
    #     Per default this exportation is switched off for performance reasons,
    #     because the extraction step is an expensive operation and is usually
    #     useless for serving static content. So one usually enables the
    #     exportation for CGI and SSI requests only.
    #   o StrictRequire:
    #     This denies access when "SSLRequireSSL" or "SSLRequire" applied even
    #     under a "Satisfy any" situation, i.e. when it applies access is denied
    #     and no other module can change it.
    #   o OptRenegotiate:
    #     This enables optimized SSL connection renegotiation handling when SSL
    #     directives are used in per-directory context.
    #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
    <FilesMatch "\.(cgi|shtml|phtml|php|php5|php4|php3)$">
        SSLOptions +StdEnvVars
    </FilesMatch>
    <Directory "C:/xampp/apache/cgi-bin">
        SSLOptions +StdEnvVars
    </Directory>

    #   SSL Protocol Adjustments:
    #   The safe and default but still SSL/TLS standard compliant shutdown
    #   approach is that mod_ssl sends the close notify alert but doesn't wait for
    #   the close notify alert from client. When you need a different shutdown
    #   approach you can use one of the following variables:
    #   o ssl-unclean-shutdown:
    #     This forces an unclean shutdown when the connection is closed, i.e. no
    #     SSL close notify alert is send or allowed to received.  This violates
    #     the SSL/TLS standard but is needed for some brain-dead browsers. Use
    #     this when you receive I/O errors because of the standard approach where
    #     mod_ssl sends the close notify alert.
    #   o ssl-accurate-shutdown:
    #     This forces an accurate shutdown when the connection is closed, i.e. a
    #     SSL close notify alert is send and mod_ssl waits for the close notify
    #     alert of the client. This is 100% SSL/TLS standard compliant, but in
    #     practice often causes hanging connections with brain-dead browsers. Use
    #     this only for browsers where you know that their SSL implementation
    #     works correctly.
    #   Notice: Most problems of broken clients are also related to the HTTP
    #   keep-alive facility, so you usually additionally want to disable
    #   keep-alive for those clients, too. Use variable "nokeepalive" for this.
    #   Similarly, one has to force some clients to use HTTP/1.0 to workaround
    #   their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
    #   "force-response-1.0" for this.
    <IfModule setenvif_module>
        BrowserMatch ".*MSIE.*" \
                 nokeepalive ssl-unclean-shutdown \
                 downgrade-1.0 force-response-1.0
    </IfModule>

    #   Per-Server Logging:
    #   The home of a custom SSL log file. Use this when you want a
    #   compact non-error SSL logfile on a virtual host basis.
    <IfModule log_config_module>
        CustomLog logs/ssl_request.log \
                  "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"
    </IfModule>
</VirtualHost>

Existe uma maneira de baixar um diretório apache inteiro, com todas as subpastas e arquivos, para um diretório local no meu computador?

Por exemplo: http://onj3.andrelouis.com/phonetones/

Este é um arquivo de toques de telefone, mas em vez de baixar cada arquivo zip individual em cada pasta individual, seria muito mais fácil, se fosse possível baixar o diretório inteiro para uma pasta no meu computador. Também seria bom, se pudesse manter os carimbos de data e hora originais nos arquivos, mas nem tenho certeza se o apache armazena esse tipo de dados.

Obrigada.

Estou usando uma linguagem dinâmica que via FFI envolve a dll wldap32. Estou usando o ApacheDS e posso me conectar perfeitamente a ele do meu cliente usando o LDAP normal. No entanto, não consigo me conectar a ele ao usar o LDAPS. Sim, a caixa de seleção está marcada para iniciar o LDAP (na porta 10636) e tudo parece bem. Na verdade, de dentro do ApacheDS eu posso abrir uma conexão com o LDAPS e funciona. O problema é do meu cliente.

O que notei é que nos logs está impresso o seguinte:

[17:28:23] WARN [org.apache.directory.server.ldap.LdapProtocolHandler] - Unexpected exception forcing session to close: sending disconnect notice to client.
javax.net.ssl.SSLException: Improper close state: Status = OK HandshakeStatus = NEED_WRAP
bytesConsumed = 0 bytesProduced = 7 sequenceNumber = 1
at org.apache.mina.filter.ssl.SslHandler.closeOutbound(SslHandler.java:497)
at org.apache.mina.filter.ssl.SslFilter.initiateClosure(SslFilter.java:762)
at org.apache.mina.filter.ssl.SslFilter.filterClose(SslFilter.java:693)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.callPreviousFilterClose(DefaultIoFilterChain.java:776)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1600(DefaultIoFilterChain.java:49)
at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.filterClose(DefaultIoFilterChain.java:1155)
at org.apache.mina.core.filterchain.IoFilterAdapter.filterClose(IoFilterAdapter.java:146)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.callPreviousFilterClose(DefaultIoFilterChain.java:776)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1600(DefaultIoFilterChain.java:49)
at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.filterClose(DefaultIoFilterChain.java:1155)
at org.apache.mina.filter.executor.ExecutorFilter.filterClose(ExecutorFilter.java:608)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.callPreviousFilterClose(DefaultIoFilterChain.java:776)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1600(DefaultIoFilterChain.java:49)
at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.filterClose(DefaultIoFilterChain.java:1155)
at org.apache.mina.core.filterchain.IoFilterAdapter.filterClose(IoFilterAdapter.java:146)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.callPreviousFilterClose(DefaultIoFilterChain.java:776)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.fireFilterClose(DefaultIoFilterChain.java:769)
at org.apache.mina.core.session.AbstractIoSession.closeNow(AbstractIoSession.java:353)
at org.apache.mina.core.service.IoHandlerAdapter.inputClosed(IoHandlerAdapter.java:102)
at org.apache.mina.core.filterchain.DefaultIoFilterChain$TailFilter.inputClosed(DefaultIoFilterChain.java:997)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextInputClosed(DefaultIoFilterChain.java:735)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:49)
at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.inputClosed(DefaultIoFilterChain.java:1119)
at org.apache.mina.core.filterchain.IoFilterAdapter.inputClosed(IoFilterAdapter.java:154)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextInputClosed(DefaultIoFilterChain.java:735)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:49)
at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.inputClosed(DefaultIoFilterChain.java:1119)
at org.apache.mina.core.filterchain.IoFilterAdapter.inputClosed(IoFilterAdapter.java:154)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextInputClosed(DefaultIoFilterChain.java:735)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:49)
at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.inputClosed(DefaultIoFilterChain.java:1119)
at org.apache.mina.core.filterchain.IoFilterAdapter.inputClosed(IoFilterAdapter.java:154)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextInputClosed(DefaultIoFilterChain.java:735)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:49)
at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.inputClosed(DefaultIoFilterChain.java:1119)
at org.apache.mina.core.filterchain.IoFilterAdapter.inputClosed(IoFilterAdapter.java:154)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextInputClosed(DefaultIoFilterChain.java:735)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.fireInputClosed(DefaultIoFilterChain.java:728)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.read(AbstractPollingIoProcessor.java:556)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.access$1200(AbstractPollingIoProcessor.java:68)
at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.process(AbstractPollingIoProcessor.java:1222)
at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.process(AbstractPollingIoProcessor.java:1211)
at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run(AbstractPollingIoProcessor.java:683)
at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:64)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)

No meu cliente C, recebo o erro "LDAP_SERVER_DOWN (81)" ao chamar a função ldap_simple_bind_s()

Isso diz alguma coisa para alguém?

Desde já, obrigado!

No site do apache, parece que a versão mais recente é 2.4.54.

Instalei o apache no meu CentOS 7, e quando verifico a versão, mostra que instalou a versão mais recente, mas o número da versão é httpd-2.4.6-97.el7.centos.5.x86_64:

# yum changelog httpd
Failed to set locale, defaulting to C
Loaded plugins: changelog, fastestmirror
Loading mirror speeds from cached hostfile
 * base: centos.interhost.net.il
 * extras: centos.interhost.net.il
 * updates: centos.interhost.net.il

Listing all changelogs

==================== Installed Packages ====================
httpd-2.4.6-97.el7.centos.5.x86_64       installed
* Thu Mar 24 14:00:00 2022 CentOS Sources <[email protected]> - 2.4.6-97.el7.centos.5
- Remove index.html, add centos-noindex.tar.gz
- change vstring
- change symlink for poweredby.png
- update welcome.conf with proper aliases

* Tue Mar 22 14:00:00 2022 Lubo? Uhliarik <[email protected]> - 2.4.6-97.5
- Resolves: #2065243 - CVE-2022-22720 httpd: HTTP request smuggling
  vulnerability in Apache HTTP Server 2.4.52 and earlier

Recebi um relatório de que o site tem vulnerabilidades de segurança, que deveriam ser corrigidas em versões anteriores do Apache, então não entendo por que tenho essa vulnerabilidade se tiver a versão mais recente.

Alguém pode explicar porque é assim?

Estou experimentando alguns sistemas Wiki pessoais para o meu computador Windows 10 que usa arquivos Markdown simples e me deparei com o GRAV . Esse é um CMS de código aberto usando a configuração Extract-and-drop que a maioria dos servidores da Web com PHP 7 podem executar.

Desde que eu experimentei o DokuWiki antes, eu já tenho o MicroApache disponível e pensei que só precisava extrair o GRAV-zip lá. Mas não inicia, talvez eu precise de um download limpo e configuração do MicroApache?

C:.
+---grav
\---server
    +---conf
    +---logs
    +---modules
    \---php
        \---ext

Editei .\server\conf\httpd.confpara usar a pasta GRAV.

# absolute minimum configuration for DokuWiki on a Stick
# change the Listen directive if you want to use a different port

Listen 8800
ServerName microapache
ServerRoot .
DocumentRoot ./../grav
ServerAdmin [email protected]

Mas tudo o que recebo ao iniciar o MicroApache é uma página da Web quebrada ...

cd server
start "Apache server" /B mapache.exe
start http://localhost:8800/

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete 
your request.

Please contact the server administrator at [email protected] to inform them of the 
time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

E não há servidor para parar

ApacheKill.exe

■ Killing all matching processes
■ Searching for processes matching "mapache.exe"
Error: A process with that name does not appear to be running

Como a maior parte da solução de problemas do GRAV é para Linux, não posso seguir esses guias na configuração do Windows.

Quando executo uma solicitação cURL no meu servidor apache2 via HTTP, a única resposta que recebo é Invalid Host header. No entanto, ao usar HTTPS, tudo parece funcionar conforme o esperado. Eu tenho a reescrita habilitada para cada site redirecionar para HTTPS. Isso ocorre em todos os subdomínios. Embora eu tenha feito algumas pesquisas, tudo o que posso encontrar são problemas relacionados ao webpack.

Eu estou apache2 2.4.52correndo ubuntu 22.04 LTS.

Aqui está o arquivo conf da minha página principal.

<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 www.example.com

    ServerAdmin webmaster@localhost
    DocumentRoot /var/www/example.com
    ServerName example.com
    ServerAlias a.example.com
    # 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} =example.com
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
</VirtualHost>

Saída decURL --head --verbose http://example.com

*   Trying <my-ip>:80...
* Connected to example.com (my-ip) port 80 (#0)
> HEAD / HTTP/1.1
> Host: example.com
> User-Agent: curl/7.84.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
< Connection: Keep-Alive
Connection: Keep-Alive
< Content-Length: 9
Content-Length: 9
< Content-Type: text/plain
Content-Type: text/plain
< Date: Sun, 24 Jul 2022 16:09:03 GMT
Date: Sun, 24 Jul 2022 16:09:03 GMT

<
* Connection #0 to host example.com left intact