Re: Problem with cookies

[Robert I. <cor...@gm...>]

Arthur,

On 7/20/07, Robert Iakobashvili <cor...@gm...> wrote:
> > > I'm thinking, has it something to do with how username:password are posted?
> > > On url1 (2nd URL in config file) I'm basically getting original login page
> > > returned with
> > > email address, which just was sent with POST, already in the text field. But
> > > no messages about incorrect login/password or anything like that. This is
> > > strange.
>
> I need to see the capture (ethereal/wireshark/tcpdump)

Sorry, for the flow of e-mails.

After some thinking, it could be that the problem is solely
in authentication, and the non-existing cookies are just the consequences.
The bugfix we did on our side seems to be optional and not a must.

Some servers/portals are not rejecting any failed authentications
by 4xx messages (like bad passwords, e-mails, etc),
but ether:
a) sending 3xx redirect to some problem describing page with subsequent
200 OK without setting to browser cookies;
b) sending 200 OK, but not setting to browser cookies;
c) etc methods;

One more place of assistance could be the web-server logs.
There are several logs in the case of apache, like access log,
authentication log, etc

Could it be that there are more parameters required by the POST form?
Could it be, that the e-mail used for authentication is not in database or
misspelled in the token/credentials file?

One more option to try is "multi-part form data POST-ing as in RFC1867".
This is a fresh feature in curl-loader without support for tokens loaded from
a file yet.

In any case packet captures (if there is an option for the
non-encrypted mode) and
curl-loader logs of headers and bodies could be of assistance.

Sincerely,
Robert Iakobashvili,
coroberti %x40 gmail %x2e com
...........................................................
http://curl-loader.sourceforge.net
A web testing and traffic generation tool.