hi
ok good something worked :).
The other thing I would try is
a. Make a request to secured page but the Authorization manager shouldnt be
in scope here (so you'll get a 401 with set-cookie )
b. Repeat the above request but with the Authorization manager in scope
Thread Group
Simple Controller
request secure
Assert 401
Simple controller
request secure
Http Auth Manager
regards
deepak
On Fri, Sep 11, 2009 at 1:02 AM, <[email protected]> wrote:
> Hi Deepak,
>
> Using the HTTpClient Httpsampler did not solve the issue but requesting a
> non-secured page before the secured one is the solution!
>
> Do you think that the reason of the issue is the fact that the http client
> behind jmeter handles the 401 response without letting know the upper layers
> of Jmeter (and therefore the cookie manager is not aware of the cookie
> present in the 401 response) ?
>
> Thanks,
> Benoit
>
> --------------------------------------------------------
>
> Legal Notice: This electronic mail and its attachments are intended solely
> for the person(s) to whom they are addressed and contain information which
> is confidential or otherwise protected from disclosure, except for the
> purpose for which they are intended. Dissemination, distribution, or
> reproduction by anyone other than the intended recipients is prohibited and
> may be illegal. If you are not an intended recipient, please immediately
> inform the sender and return the electronic mail and its attachments and
> destroy any copies which may be in your possession. UCB screens electronic
> mails for viruses but does not warrant that this electronic mail is free of
> any viruses. UCB accepts no liability for any damage caused by any virus
> transmitted by this electronic mail. (Ref: #*UG1107)
> --------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
