> > (Note that there are no cookies trapped by
> CatchURL
> > except the google-analytics ("__utm...") and PHP
> > Session ID is the only cookie the server sends
> > *after* the login is successful.)
> > 
> > Other than that, are there any thoughts on how to
> > work around it?  Or am I missing/misinterpreting
> > what's going on?>
> 
> The session ID is precisely what the capture url
> should have so Httrack can take over from there.
>


Any idea why CatchURL does not detect it?  The only cookies CatchURL detects
are the google-analytics ones.  The PHP session ID is what I see when I look
at the cookies via Firefox.  Also, unless it is some hash of the
form_build_id, the session ID seems to be unrelated to that number.


In case I wasn't clear earlier, let me re-state:
there are NO cookies trapped by CatchURL except the google-analytics
("__utm...").  Period.  The PHP Session ID is the only other cookie the server
sends *after* the login is successful, *not* during the login attempt recorded
by CatchURL.