Re: mod_setenvif/4545: No way to limit access based on REMOTE_IDENT RFC1413 identd IdentityCheck

[co...@apache.org]

[In order for any reply to be added to the PR database, you need]
[to include <ap...@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]


Synopsis: No way to limit access based on REMOTE_IDENT RFC1413 identd IdentityCheck

State-Changed-From-To: open-analyzed
State-Changed-By: coar
State-Changed-When: Sun Jul  4 11:33:34 PDT 1999
State-Changed-Why:

In the Apache model, access checking occurs before
authentication and authorisation checking -- and all
of these occur before content handling.  So the
information should never reach a CGI script, for
instance, because the access decision should have
been made much earlier.

You might check out the mod_access_identd module, which
is available from <http://Web.MeepZor.Com/packages/>.