Empresas
Empleos
  • Sobre nosotros
  • Soluciones
    • Publicación de vacantes
      Publica tu vacante y recibe candidatos calificados en 48h.
    • Evaluación de candidatos
      500+ pruebas técnicas y psicológicas, más anti-fraude.
    • Headhunting
      Búsqueda ejecutiva a la medida de principio a fin.
    • Nómina + EOR
      Dispersión de nómina y EOR en más de 15 países de LATAM.
  • Precios
  • Empleos

0

683
Vistas
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 la pregunta
Encuentra empleos remotos

¡Descubre la nueva forma de encontrar empleo!

Top de empleos
Top categorías de empleo
Empresas
Publicar vacante Precios Comercial
Legal
Términos y condiciones Política de privacidad
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomiéndame algunas ofertas
Necesito ayuda