Administration
  Home arrow Administration arrow Page 3 - Getting More Out Of Apache (Part 2)
Dev Shed Forums 
Administration  
Apache  
BrainDump  
DHTML  
Flash  
Java  
JavaScript  
Multimedia  
MySQL  
Oracle  
Perl  
PHP  
Practices  
Python  
Reviews  
Security  
Style-Sheets  
Web Services  
XML  
Zend  
Zope  
Forums Sitemap 
IBM® developerWorks 
Dedicated Servers 
E-Commerce Hosting 
Linux Web Hosting 
Managed Hosting 
Small Business Hosting 
Download TestComplete 
VPS Hosting 
Weekly Newsletter

 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
ADMINISTRATION

Getting More Out Of Apache (Part 2)
By: icarus, (c) Melonfire
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 5 stars5 stars5 stars5 stars5 stars / 1
    2001-01-23

    Table of Contents:
  • Getting More Out Of Apache (Part 2)
  • Eyes Only
  • Identity Check
  • Grouping Things Together
  • Timmmmmmbbbbberrrr!
  • When Things Go Wrong
  • Just Rewrite It!
  • Putting It Into Practice

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
     
    ADVERTISEMENT

    Stay one step ahead of the competition. Evaluate and give feedback on some of the hottest web development tools on the market today. Make your opinion heard! Click Here

    Getting More Out Of Apache (Part 2) - Identity Check
    (Page 3 of 8 )

    If you've been paying attention, you'll have noticed that there's one thingmissing - the authorization file itself. And Apache comes with its ownlittle utility to create the file - it's called "htpasswd".

    Switch to the directory specified in the AuthUserFile directive above, adrun the "htpasswd" command to create a file containing authorized users -you might see something like this:

    $ htpasswd -c users joe Adding password for joe. New password: Re-type new password:
    And if you peek into the file "users", you'll see that the user has beenadded to the file - the garbage next to the user name is the password youjust entered, in encrypted form.

    $ cat users joe:9DyNcHx.8JOp2
    You can add as many users as you like using the method above (remember toomit the -c parameter, though, since that's only used when creating a filefor the first time).

    With everything in place, start up your browser and point it to thedirectory you just protected. The Web server should immediately pop up adialog box asking for a username and password, and will only allow youto view the contents of the directory if you enter the correct values.Ain't that cool?

    More Administration Articles
    More By icarus, (c) Melonfire


     

       

    ADMINISTRATION ARTICLES

    - Configuring Load-Balanced Clusters
    - Load-Balanced Clusters
    - UNIX Time Format Demystified
    - Making Changes in the CVS
    - Building Your First CVS Repository
    - CVS Quickstart Guide
    - Authorizing Users in Samba
    - Handling User Accounts in Samba
    - Authentication in Samba
    - Accounts, Authentication, and Authorization
    - Advanced Concepts on Dealing with Files and ...
    - Dealing with Files and Filesystems
    - More Hacks for the User Environment in BSD
    - Personalizing the User Environment in BSD
    - Customizing the User Environment in BSD

     
    Accelerating Trading Partner Performance
     
    Competing on Analytics
     
    Cost Effective Scaling with Virtualization and Coyote Point Systems
     
    Five Checkpoints to Implementing IP Telephony
     
    Hosted Email Security: Staying Ahead of New Threats
     




    © 2003-2008 by Developer Shed. All rights reserved. DS Cluster 1 hosted by Hostway