I've created a Test plan that uses a regex post processor to extract the session id from the response headers of the first request so it can be sent in subsequent posts. The regex post processor gives the option to search the response body or headers but doesn't appear to save this setting as on every load of the test plan I have to reselect the headers option. This behaviour is annoying to say the least and I'm wondering how it will behave under remote testing. We're using JDK1.4.1_02 Andrew
1) the post-processor should be a child of the sampler to which it applies, otherwise it will be applied to all the samplers at the same level 2) regexes only return what you tell them to - make sure you enclose some or all of the regex in parentheses. e.g. .* will match everything, but return nothing (.*) will match and return everything. Please try this and if it still does not work, add a sample test plan to this issue as an attachment
Created attachment 12916 [details] Simple Test plan to demonstrate problem
Sebb, The problem is not in the pattern matching but in the gui behaviour of the post processor. On screen I'm given the option to select eith body of header for the post processor to search. I need to select header but when I move off the post processor and move back to it my selection is lost and it defaults to search body. Even if I select header and save the test plan next time I re open it body will be selected. I've attached a very simple test plan that you can hopefully use to see the problem. The test plan probably doesn't even run but this isn't required to show the error. Andrew
Sorry, my previous reply was not relevant - I posted the reply in the wrong place ... == The loss of the header/body setting is a known bug, fixed in CVS after 2.0.1 was released. If you don't want to wait for the next release, you could perhaps try one of the nightly builds (linked from JMeter home page). BTW, remote testing is not very performant compared with non-GUI mode. There have been several discussions of this on the User list. *** This bug has been marked as a duplicate of 29853 ***
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/1454