hi ok , if you have access to a developer then you can probably ask him whats causing the 403 since he can see the logs and can see whats failing.
The browser doesnt generate any cookies by itself so any cookies have to come from the app. You can have two cookies with the same name so long as they are scoped to different paths or domains (you should see this in set-cookie) - otherwise last one wins. Portals generally use a lot of dynamic URLs and dynamic data so you should check that as well too. Beyond this unless you send a trace from browser v/s a trace from Jmeter theres not much more we can help you with. regards deepak On Mon, Aug 23, 2010 at 8:54 PM, cal0y <[email protected]>wrote: > > I started with a clean browser and I'm still getting the 403, and the > initial > loading of the homepage does have a jsessionid. Not sure if the app sends > it > to the browser though. I have also checked the http headers and there are > no > authorization headers. Our application use portlets by the way.I have > noticed in the cookie manager of firebug that the page has 2 jsessionid's. > I > asked one our developers about it and he said that the theme runs as a > separate application and that probably causes the other jsessionid. Is this > a problem?regards-cal0y > -- > View this message in context: > http://jmeter.512774.n5.nabble.com/Jmeter-gets-response-code-403-on-post-methods-tp2645078p2650714.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] > >
