> How can one verify what kind of verification a 
website
> is using ?> I'm trying to get the password thing to work but I
> allways get rejected from the server. I've tried all
> things the manual lists.

Several authentication systems can be used, generally 
you have 3 solutions:

1. Form based authentication
You get a login/password HTML page, sometimes with 
some buttons or optional checkboxes
This can ONLY be captured using "ADD URL"/"CAPTURE" 
because the POST request which is used is impossible 
to "catch" with another solution. If you capture the 
page using standard options (that is, enter the URL of 
the page, and mirror it), you'll only get the login 
page, and entering username/password/clicking on the 
login button will put you to an online page.

2. Basic authentication
You get, the first time you are trying to access the 
page, an alert box where you have to enter both 
username/password
If you capture the page using standard options (that 
is, enter the URL of the page, and mirror it), you'll 
get an error page ("Unauthorized" or something 
similar).
This can be captured using the username:password 
scheme URL, as in:  
<http://smith:foobar@www.yoursite.abc/>...

3. Challenged authentication
Same as basic auth, but with a "domain", and a 
challenge sent by the server. 
This kind of authentication is NOT yet managed!
If you capture the page using standard options, you'll 
only get an error page (Unauthorized).

Here are the most frequent cases, but many websites 
also mix cookies or other things, which causes mirror 
to be much more difficult. 

Another problem is the mirror process itself: some 
pages have a "logout" link, which destroy the cookie. 
Problem: after having followed this link, HTTrack 
won't be able to mirror the rest of the website..

Be sure that you defined proper filters (see the FAQ), 
and used proper mirror method (either 
username:password@yourURL or the "capture" tool). Some 
sites won't work, however.