How to Check Which Apache Modules are Enabled/Loaded in Linux

Best Affordable Linux and WordPress Services For Your Business
Outsource Your Linux and WordPress Project and Get it Promptly Completed Remotely and Delivered Online.

If You Appreciate What We Do Here On TecMint, You Should Consider:

  1. Stay Connected to: Twitter | Facebook | Google Plus
  2. Subscribe to our email updates: Sign Up Now
  3. Get your own self-hosted blog with a Free Domain at ($3.45/month).
  4. Become a Supporter - Make a contribution via PayPal
  5. Support us by purchasing our premium books in PDF format.
  6. Support us by taking our online Linux courses

We are thankful for your never ending support.

Aaron Kili

Aaron Kili is a Linux and F.O.S.S enthusiast, an upcoming Linux SysAdmin, web developer, and currently a content creator for TecMint who loves working with computers and strongly believes in sharing knowledge.

Your name can also be listed here. Got a tip? Submit it here to become an TecMint author.

RedHat RHCE and RHCSA Certification Book
Linux Foundation LFCS and LFCE Certification Preparation Guide

You may also like...

11 Responses

  1. ANIL says:

    Can i know the modules path using apachectl ?

  2. Tomas says:

    Aaron, have you actually tried disabling these modules yourself? I have, and I had issues.

    Apache server comes with MPM prefork by default (at least on RHEL 7), therefore you cannot simply disable mpm_prefork_module.

    You also need to load a CGI module appropriate to the MPM, therefore mod_cgi with the prefork MPM.

    • Aaron Kili says:


      As i stated, “It is perhaps a good idea to know why you want disable a certain module(s) before actually doing that”. The effects of disabling these modules various from one user’s system to another. Therefore, if you get issues afterwards, you probably need them, you can enable them once again.

      However, thanks for mentioning that, i hope Apache users out there will benefit from your feedback.

      • Tomas says:

        The idea is pretty simple, why would you have dozens of auth* modules loaded if you don’t use them? It’s wiser to disable them unless you have a reason not to. Performance is always a bonus, but not my main concert when it comes to auth* modules.

        And you haven’t answered my question really.

  3. Sado says:

    You seem to have a lot of auth* modules loaded?

    Do you know which ones are reasonably save to disable on Apache (say on CentOS 7)?

    • Aaron Kili says:


      All modules you are seeing from the output of the command in the article are the ones loaded by default on Linux Mint(Ubuntu base). It is perhaps a good idea to know why you want disable a certain module(s) before actually doing that.

      However, since apache loads all these modules into memory, this can heavily reduce your memory and system performance. You may consider disabling the modules below:

      mpm_prefork_module (static)
      authn_alias_module (shared)
      authn_anon_module (shared)
      authn_dbm_module (shared)
      authn_default_module (shared)
      authz_owner_module (shared)
      authz_dbm_module (shared)
      authz_default_module (shared)
      ldap_module (shared)
      authnz_ldap_module (shared)
      include_module (shared)
      env_module (shared)
      ext_filter_module (shared)
      mime_magic_module (shared)
      usertrack_module (shared)
      dav_module (shared)
      status_module (shared)
      autoindex_module (shared)
      info_module (shared)
      dav_fs_module (shared)
      vhost_alias_module (shared)
      negotiation_module (shared)
      actions_module (shared)
      speling_module (shared)
      userdir_module (shared)
      substitute_module (shared)
      proxy_balancer_module (shared)
      proxy_ftp_module (shared)
      proxy_http_module (shared)
      proxy_ajp_module (shared)
      proxy_connect_module (shared)
      cache_module (shared)
      suexec_module (shared)
      disk_cache_module (shared)
      cgi_module (shared)
      version_module (shared)

      Once you have turned off any module(s), you can enable it again, that is if you need to use it.

      • kenny says:

        if they are marked shared is this means they are disabled?

        • Tomas says:

          No. If it says “static” then such module has been compiled into the httpd binary when the server was built. This module will always be present while running Apache.

          If it says “shared” then such module has to be loaded dynamically by using the LoadModule directive.

        • Aaron Kili says:


          Not really, static modules are compiled into the Apache binary when the package is built, whereas dynamic shared modules are included at runtime.

Got something to say? Join the discussion.

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.