https://bz.apache.org/bugzilla/show_bug.cgi?id=64209
--- Comment #7 from jatinder <[email protected]> --- Here is my understanding from what is happening 1. On clicking the search scope button for the first time, the url invoked is *actionProcessor.jsp and this is same for first time, second time and so on. 2. Next request *openWithHeaders.jsp is the second request in after redirection. For the successful selection for first time, we do not see any of the parameters being URL encoded. But after first time selection, second time onwards, we do see that WinName and reportName fields do have URL Encode option checked. 3. there are few pages inbetween like *frameHdn.html, *loading.html, *header.jsp, *Scripts.jsp that do bring more informaiton on the page. 4. Next request *openwithObjectMain.jsp request in successful request have winName not having %2F characters but in the failed requests winName have %2F characters and reportName do not have %2F encoding characters thus at this point the two requests are completely different. 5. Final request which is correctly shown as *viewPageReport.jsp in successful request but it is an invalid request in failed selection request Expected - 559 /trivpt1/html/en/default/reportTemplate/viewPageReport.jsp parameters - propertyId 208133 false text/plain true projectId 1 false text/plain true refSpecTypeId 10002093 false text/plain true passThrough false false text/plain true reportTemplId 143615 false text/plain true reportName cstCountry+-+Find+-+Country+for+Documentum+System+Country false text/plain true altGuiListId -1 false text/plain true ffCnt 1 false text/plain true ffn1 triNameTX false text/plain true ffv1 false text/plain true smartField 1 false text/plain true associatedId 225581648 false text/plain true manager 1 false text/plain true parentSOSubCategoryId 1 false text/plain true selectType single false text/plain true tempSpecId 727193449844299074 false text/plain true olv 1 false text/plain true bookmarkable false false text/plain true MGRiODZhYTk5NGZj Vq-RF8cPq1GQG6-X_LWVwlisS9B61eNI false text/plain true Response - HTTP 200 Actual - 570 /trivpt1/html/en/default/common/%2Ftrivpt1%2Fhtml%2Fen%2Fdefault%2FreportTemplate%2FviewPageReport.jsp%3FpropertyId%3D208133&projectId=1&refSpecTypeId=10002093&passThrough=false&reportTemplId=143615&reportName=cstCountry+-+Find+-+Country+for+Documentum+System+Country&altGuiListId=-1&ffCnt=1&ffn1=triNameTX&ffv1=&smartField=1&associatedId=225581648&manager=1&parentSOSubCategoryId=1&selectType=single&tempSpecId=727193449844299074&olv=1&bookmarkable=false Response - HTTP 404 Ultimately, I think while parsing some of the these requests, Jmeter decides to change how it understands the request and parameters and what parameters are to be url encoded. For the first request is does correctly and then for second request it does it differently then how it did for the first time. This creates requests which are not understood to server. -- You are receiving this mail because: You are the assignee for the bug.
