> > Can httrack not set cookie when expires is before
> > now (browsers don't)
> HTT doesn't do anything special with them. If
> they're coming from the server expired that is what
> HTT stores.
> 
> Is the site password protected and did you have HTT
> log in? HTTrack Help: Authentication
> <http://httrack.kauler.com/help/Authentication>
> 
> 
> 
> 

Well it's the login page which is not protected and there's obviously a bug in
the site as they try set a bad cookie (wrong exp time) for their own purpose
(not HTT authentication whatsoever) so the browser does not store this cookie
but on subsequent request HTT sends the bad cookie back and the site reacts as
it is an error (in fact it is because the cookie should never being resent as
it is a bad one).
My point is if you store a "bad" cookie : it shouldn't be done according to
the RFP.
I made a workaround with a wrapper but I may not be the only one with this
case.