Empresas
Empregos
  • Sobre nós
  • Soluções
    • Publicação de vagas
      Publique sua vaga e receba candidatos qualificados em 48h.
    • Avaliações de candidatos
      Mais de 500 testes técnicos e psicológicos, mais anti-fraude.
    • Headhunting
      Busca executiva personalizada do início ao fim.
    • Folha de Pagamento + EOR
      Dispersão de folha e EOR em mais de 15 países da LATAM.
  • Preços
  • Empregos

0

688
Visualizações
Apache and IBM WAS, was_ap24_module only for specified <Location> possible?

we are running an IBM WAS and an Apache 2.4 in front of it. It works well, but at the moment it seems that most benefits of Apache can't be used, as all the traffic is routed directly and exclusively to IBM WAS.

Current httpd.conf:

...
LoadModule was_ap24_module [..]/WebSphere/Plugins/bin/64bits/mod_was_ap24_http.so
WebSpherePluginConfig [..]/WebSphere/Plugins/config/rbi_ihs_m/backend_plugin-cfg.xml
...
LoadModule ssl_module etc/httpd/modules/mod_ssl.so
<IfModule mod_ssl.c>
  Listen 1443
  <VirtualHost *:1443>
    SSLEngine on
    ...[noting IBM WAS relevant]
  </VirtualHost>
</IfModule>
...

We would like to:

  1. Serve some pages by Apache from file system and not through IBM WAS. E.g. a mix of native Apache and IBM WAS. Is this possible? We tried with a specific but it seems that the WAS module is getting all the traffic and the <Location /not_was/*> is ignored.

  2. Serve some WAS Pages with Basic Auth. E.g using <Location /was_protected/*> and asking first for user + password and only then forwarding to IBM WAS. Is this possible?

Many thanks in advance!

over 4 years ago · Santiago Trujillo
Responde à pergunta
Encontrar trabalhos remotos

Descubra a nova forma de encontrar um emprego!

melhores empregos
Principais categorias de trabalho
Empresas
Postar vaga Preços Comercial
Jurídico
Termos e Condições Política de privacidade
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomende algumas ofertas para mim
Preciso de ajuda