\label{Guts_Apache_Modules}
\begin{figure}
\begin{lyxcode}
<LocationMatch~\char`\"{}\textasciicircum{}/res.{*}\char`\"{}>

PerlAccessHandler~~~~~~~Apache::lonacc

PerlHeaderParserHandler~Apache::lonrep

ErrorDocument~~~~~403~/adm/login

ErrorDocument~~~~~404~/adm/notfound.html

ErrorDocument~~~~~406~/adm/roles

ErrorDocument~~~~~500~/adm/errorhandler

</LocationMatch>

<LocationMatch~\char`\"{}\textasciicircum{}/priv.{*}\char`\"{}>

PerlAccessHandler~Apache::loncacc

SetHandler~~~~~~~~perl-script

PerlHandler~~~~~~~Apache::lonconstruct

ErrorDocument~~~~~403~/adm/login

ErrorDocument~~~~~404~/adm/notfound.html

ErrorDocument~~~~~406~/adm/unauthorized.html

ErrorDocument~~~~~500~/adm/errorhandler

</LocationMatch>
\end{lyxcode}

\caption{\label{loncapa_apache.conf example}\texttt{loncapa\_apache.conf}
example snippet}
\end{figure}
Which chain of handler deals with which kind of resource is defined
in \texttt{/etc/httdp/conf/loncapa\_apache.conf}. LON-CAPA only defines
handlers at the header-parser, access control, and response phase
(figure 3-3 Eagle book). In the header-parser phase, the replication
handler is run, and in the access-control phase, the various access-handlers.
Future handlers will mostly be implemented in the response phase.
Fig. \ref{loncapa_apache.conf example} shows excerpts of the configuration
script \texttt{/etc/httpd/loncapa\_apache.conf} for these modules.