Uploaded image for project: 'JBoss Web Server'
  1. JBoss Web Server
  2. JWS-53

mod_proxy configuration is ambiguous and inconsistent across platforms

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • JWS 3.0.0 ER1
    • JWS 3.0.0 ER1
    • httpd
    • None

      mod_proxy example configuration should reside in a one file and it should be consistent across our supported platforms.

      At the moment, with ER1:

      • Windows zips contain conf.d/proxy_ajp.conf.in that is ignored by postinstall and remains with .in suffix, whereas conf.modules.d/00-proxy.conf is loaded by default. This leaves mod_proxy_ajp not loaded by default, which is a regression from DR3.
      • On the other hand, RHEL zips contain both conf.d/proxy_ajp.conf and conf.modules.d/00-proxy.conf without any need for renaming from .in to .conf.

      Call to action

      • Add LoadModule proxy_ajp_module modules/mod_proxy_ajp.so to conf.modules.d/00-proxy.conf for all platforms.
      • Remove LoadModule proxy_ajp_module modules/mod_proxy_ajp.so from conf.d/proxy_ajp.conf on all platforms (i.e. leave only that commented example in the file as it is now).
      • Rename all instances of conf.d/proxy_ajp.conf.in to conf.d/proxy_ajp.conf on all platforms.

      Reasoning

      • conf.modules.d/00-proxy.conf should be responsible for loading all mod_proxy modules, as it is stated in its header.
      • We want to provide our customers the mod_proxy_ajp example in conf.d/proxy_ajp.conf as it has been provided before.
      • We want consistency across platforms, i.e. no conf.d/proxy_ajp.conf.in / conf.d/proxy_ajp.conf discrepancies.

      Thoughts? Comments?

            rhn-engineering-mturk Mladen Turk
            mbabacek1@redhat.com Michal Karm
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: