Using what I have experienced during tests using JMeter, HTTP 403 Forbidden could be caused by:
- a missing HTTP Cookie Manager, if your application session is cookie-based - a session variable that needs to be sent in later requests (POST or GET parameters): add an post-processor, Regex for example, to a prior request which response has the identifier needed. - a resubmitted request (not all cases): some requests, when captured using JMeter HTTP Proxy Server, are submitted two or more times because an HTTP 302 could be returned. In these cases, uncheck "Follow redirection" option in HTTP Request sampler for all samplers that should return HTTP 302 (Adding a View Result Tree Listener and executing a test with 1 thread should help). - application's login credentials used are invalid, forbidden or were expired Hope it helps. Flávio Cysne 2012/9/10 Dzmitry_Kashlach <[email protected]> > I'm not sure, but have you authorized on server? Do you use > http://blazemeter.com/blog/using-http-cookie-manager-jmeter-not-cookie-jar > HTTP Cookie Manager in Thread Group? > Try to use it. > > > > -- > View this message in context: > http://jmeter.512774.n5.nabble.com/Response-message-Forbidden-tp5714673p5714711.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] > >
