Well, one way to handle the authentication requirements of a web-site, in an LDAP-based intranet environment, is to simply let the web server protect the entire site. Both Apache and (especially...) IIS can do this. The web server has the magical means to determine who the requesting internal user is, and of course to distinguish internal users from outsiders. Unauthorized users simply can’t reach the site at all. Furthermore, those that do, have available credentials that the CGI program can query if further authentication logic within the site needs to use it. (Internet users are automatically excluded.)
This is one key way in which “intra-net” web sites are able to play by very different and much-simplified rules, versus those of the “wild and wooly” Internet-at-large. If you simply want to restrict the entire site, you don’t have to write protective logic into the site at all. The site is inside the fortress, and they’re checking badges at the door, and there’s no other way to get inside, and ... and that’s it. (“Schweet!”)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
