Yes I see that the SSSid changes every time ( and Jmeter uses the same sssid ) , how do I corect this
Deepak Shetty wrote: > > hi > > It doesnt look like your login was successful , because the server has > thrown back the login page. As repeatedly mentioned , what does your > browser > post and what does it get in return when the login is successful. You need > to compare that carefully with your jmeter request. > In your request you have a parameter called ssid .. what is this value? > does > it differ for every request? if so are you extracting it correctly from > the > previous request? > > Why do you expect password in the response? Your app shouldnt be sending > back the password > regards > deepak > > > > On Tue, Sep 1, 2009 at 1:05 PM, vijay1507 <[email protected]> wrote: > >> >> Thanks for your reply , >> >> >> I have tried inthe browser and was sucessful >> >> but in jmeter I am not getting the password in the response ( I can see >> it >> inthe request ) >> >> can you help me inthis regard >> >> >> >> >> Adrian Speteanu wrote: >> > >> > it is also good to get the request you make in jmeter (copy it from >> > the Request tab in the Results tree) and use it directly in the >> > browser, see if it works there. >> > >> > check if the login is successful in the browser like you do it in >> > jmeter first. if it works in the browser and not in jmeter, then you >> > need to find out what you are doing wrong. >> > >> > On Tue, Sep 1, 2009 at 3:04 AM, Deepak Shetty<[email protected]> wrote: >> >> hi >> >> first using livehttpheaders on firefox check what your browser sends , >> >> what >> >> it gets returned , how your app manages session ids etc - url or >> cookie, >> >> whether any additional tokens are passed. Once you have understood it >> >> then >> >> compare with what you are doing in Jmeter. , using View Results tree >> you >> >> can >> >> check what data /cookies are being sent. >> >> so a. You need to verify that pages that you request , you are sending >> >> the >> >> correct session id and not some recorded one . >> >> b. You need to verify that your login was indeed successful ... you >> need >> >> to >> >> check that th request that does the actual login did not get any error >> >> (you'll need to compare what your browser sends on success) >> >> >> >> regards >> >> deepak >> >> >> >> On Mon, Aug 31, 2009 at 4:45 PM, vijay1507 <[email protected]> >> >> wrote: >> >> >> >>> >> >>> Hi Deepak, >> >>> >> >>> Thanks for your reply ,I have been searching the forum all day , >> tried >> >>> cookie manager and HTTP Authorization Manager and Login Config >> Element >> >>> but >> >>> could not proceed >> >>> >> >>> Please help me !!! >> >>> -- >> >>> View this message in context: >> >>> http://www.nabble.com/Jmeter-Login-page-tp25231798p25232189.html >> >>> Sent from the JMeter - User mailing list archive at Nabble.com. >> >>> >> >>> >> >>> --------------------------------------------------------------------- >> >>> To unsubscribe, e-mail: [email protected] >> >>> For additional commands, e-mail: [email protected] >> >>> >> >>> >> >> >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] >> > >> > >> > >> http://www.nabble.com/file/p25244304/New%2BBitmap%2BImage.jpeg >> http://www.nabble.com/file/p25244304/request%2Band%2Bresponse.doc >> request+and+response.doc >> -- >> View this message in context: >> http://www.nabble.com/Jmeter-Login-page-tp25231798p25244304.html >> Sent from the JMeter - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > -- View this message in context: http://www.nabble.com/Jmeter-Login-page-tp25231798p25260475.html Sent from the JMeter - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
