Benny Rogiers is out of the office.
I will be out of the office starting 16/03/2007 and will not return until 20/03/2007. I will respond to your message when I return.
Re: Baffled with cookie manager
On 18/03/07, robert lazarski <[EMAIL PROTECTED]> wrote: On 3/18/07, robert lazarski <[EMAIL PROTECTED]> wrote: > On 3/18/07, sebb <[EMAIL PROTECTED]> wrote: > > But if it needs is_isc_rpc=true, then either that needs to be provided > > via the URL or via the POST data. > > > > A well-written application will accept the parameter as POST data as > > well as in the URL, assuming that it handles POST. > > > > All the code uses request.getQueryString() to get the params. AFAIK, > that means it can't use post data, just the url. And the only way I > can get past the authentication is using ;jsessionid - as I just can't > seem to mimmick the way those cookies are being set. Am I right in > understanding that ;jsessionid and url param passing don't mix ? > > Thanks, > Robert > The ;jsessionid entry has to before the url params, in this form: /at/smartclient.form;jsessionid=54C636E67C40F36F3A56260C3B5CC798?is_isc_rpc=true&isc_clientVersion=5.6b2&iscTNum=0 Man did I learn alot about the inner workings of http by solving this problem from beginning to end. Thanks alot Sebb, you were extremely helpful. Glad it's been sorted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Baffled with cookie manager
On 3/18/07, robert lazarski <[EMAIL PROTECTED]> wrote: On 3/18/07, sebb <[EMAIL PROTECTED]> wrote: > But if it needs is_isc_rpc=true, then either that needs to be provided > via the URL or via the POST data. > > A well-written application will accept the parameter as POST data as > well as in the URL, assuming that it handles POST. > All the code uses request.getQueryString() to get the params. AFAIK, that means it can't use post data, just the url. And the only way I can get past the authentication is using ;jsessionid - as I just can't seem to mimmick the way those cookies are being set. Am I right in understanding that ;jsessionid and url param passing don't mix ? Thanks, Robert The ;jsessionid entry has to before the url params, in this form: /at/smartclient.form;jsessionid=54C636E67C40F36F3A56260C3B5CC798?is_isc_rpc=true&isc_clientVersion=5.6b2&iscTNum=0 Man did I learn alot about the inner workings of http by solving this problem from beginning to end. Thanks alot Sebb, you were extremely helpful. Robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to ignore unwanted responce from total responce?
Hi,all is there any way with jmeter to ignore unwanted responce from total responce? can we use pre-processor to avoid some unwanted responce for TCPSampler request? Thanks in advance. Alpesh
Re: Baffled with cookie manager
On 3/18/07, sebb <[EMAIL PROTECTED]> wrote: But if it needs is_isc_rpc=true, then either that needs to be provided via the URL or via the POST data. A well-written application will accept the parameter as POST data as well as in the URL, assuming that it handles POST. All the code uses request.getQueryString() to get the params. AFAIK, that means it can't use post data, just the url. And the only way I can get past the authentication is using ;jsessionid - as I just can't seem to mimmick the way those cookies are being set. Am I right in understanding that ;jsessionid and url param passing don't mix ? Thanks, Robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HTTPS: SSL instead of TLS
OK, try again - new property as it does something different. I kept the old property for now in case you need to play with both. https.socket.protocols=prot1 prot2 ... protn i.e. space separated list of protocols. If you don't know what is supported, just use an invalid protocol and it will log the supported ones. This is in nightly build r519694 just uploaded. S/// On 18/03/07, sebb <[EMAIL PROTECTED]> wrote: OK, I'm looking into enhancing the Socket factory code to try and fix this. S/// On 18/03/07, Steffen Oehme <[EMAIL PROTECTED]> wrote: > I did some testing but it doesn't work: > https.default.protocol=SSLv3 in user.properties > JMeter picks this up correctly (as per jmeter.log) > The WebLogic server still gives the TLS Error Message > > Don't you need to set the actual protocol with setEnabledProtocols of > SSLSocket? Not familar with this, but from the API it seems as if this > is the only way to specify exactly what protocol should be used. > > The getInstance of SSLContext that you used may not exclude TLS.. At > least the description makes me believe so: > SSL Supports some version of SSL; may support other versions > SSLv2 Supports SSL version 2 or higher > SSLv3 Supports SSL version 3; may support other versions > TLS Supports some version of TLS; may support other versions > TLSv1 Supports TLS version 1; may support other versions > > sebb schrieb: > > https.default.protocol=TLS > > - > 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]
Re: Baffled with cookie manager
On 18/03/07, robert lazarski <[EMAIL PROTECTED]> wrote:
On 3/18/07, sebb <[EMAIL PROTECTED]> wrote:
> On 18/03/07, robert lazarski <[EMAIL PROTECTED]> wrote:
> > On 3/17/07, sebb <[EMAIL PROTECTED]> wrote:
> >
> > >
> > > The above line is not a standard HTTP header - or is there a blank
> > > line missing before it?
> >
> > Here's the entire request - after login - I'm capturing from wireshark
> > run from the browser:
> >
> > Hypertext Transfer Protocol
> >POST
/at/smartclient.form?is_isc_rpc=true&isc_clientVersion=5.6b2&iscTNum=0
> > HTTP/1.1\r\n
> >Request Method: POST
> >Request URI:
> > /at/smartclient.form?is_isc_rpc=true&isc_clientVersion=5.6b2&iscTNum=0
> >Request Version: HTTP/1.1
> >Host: penguin.wazollc.net:8080\r\n
> >User-Agent: Mozilla/5.0 (X11; U; Linux i686; pt-BR; rv:1.8.1.2)
> > Gecko/20070220 Firefox/2.0.0.2\r\n
> >Accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5\r\n
> >Accept-Language: pt-br,pt;q=0.8,en-us;q=0.5,en;q=0.3\r\n
> >Accept-Encoding: gzip,deflate\r\n
> >Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7\r\n
> >Keep-Alive: 300\r\n
> >Connection: keep-alive\r\n
> >Referer: http://penguin.wazollc.net:8080/at/\r\n
> >Cookie: JSESSIONID=0AC67AD80A700A57714DA7E22BAFF574\r\n
> >Content-Type: application/x-www-form-urlencoded\r\n
> >Content-Length: 3437
> >\r\n
> > Line-based text data: application/x-www-form-urlencoded
> >
_transaction=%3Ctransaction+xmlns%3Axsi%3D%22http%3A%2F%2Fwww.w3.org%2F2000%2F10%2FXMLSchema-instance%22+xsi%3Atype%3D%22xsd%3AObject%22%3E%3CtransactionNum+xsi%3Atype%3D%22xsd%3Along%22%3E0%3C%2FtransactionNum%3E%3Coperations+xsi%3Atype%3
> >
> > How do I send Line-based text data ? Do I need to set the headers Content-*
?
>
>
> That's a bit clearer; I assume that "Line-based text data:
> application/x-www-form-urlencoded" is a header added by Wireshark, so
> the actual data is the stuff starting with:
>
> _transaction=
>
> This is a standard encoded POST message; all you need to do is to add
> the appropriate parameters to the HTTP POST sampler.
>
> In this case, the parameters are a bit tricky to determine, but
> Wireshark may do it for you, or I found the following decoder page:
>
> http://ostermiller.org/calc/encode.html
>
> Or you can try using the HTTP Proxy recorder. Read the manual for details.
>
I'm all so close. Inside the code I didn't write we do:
public static boolean isRPC(HttpServletRequest httpservletrequest)
{
String s = httpservletrequest.getQueryString();
if(s == null)
return false;
else
return s.indexOf("is_isc_rpc=true") != -1;
}
Working httpservletrequest.getQueryString() from browser -->
is_isc_rpc=true&isc_clientVersion=5.6b2&iscTNum=0
From JMeter is null. I think this is because I put the ;jsession tag
on the url to associate the cookie:
POST
http://penguin.wazollc.net:8080/at/smartclient.form;jsessionid=C9981CC5C312D62EFED889AE5816A841
And passing the is_isc_rpc=true via a param. Hopefully this is the
last question - thanks for the help!
No idea what that code does.
But if it needs is_isc_rpc=true, then either that needs to be provided
via the URL or via the POST data.
A well-written application will accept the parameter as POST data as
well as in the URL, assuming that it handles POST.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Baffled with cookie manager
On 3/18/07, sebb <[EMAIL PROTECTED]> wrote:
On 18/03/07, robert lazarski <[EMAIL PROTECTED]> wrote:
> On 3/17/07, sebb <[EMAIL PROTECTED]> wrote:
>
> >
> > The above line is not a standard HTTP header - or is there a blank
> > line missing before it?
>
> Here's the entire request - after login - I'm capturing from wireshark
> run from the browser:
>
> Hypertext Transfer Protocol
>POST /at/smartclient.form?is_isc_rpc=true&isc_clientVersion=5.6b2&iscTNum=0
> HTTP/1.1\r\n
>Request Method: POST
>Request URI:
> /at/smartclient.form?is_isc_rpc=true&isc_clientVersion=5.6b2&iscTNum=0
>Request Version: HTTP/1.1
>Host: penguin.wazollc.net:8080\r\n
>User-Agent: Mozilla/5.0 (X11; U; Linux i686; pt-BR; rv:1.8.1.2)
> Gecko/20070220 Firefox/2.0.0.2\r\n
>Accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5\r\n
>Accept-Language: pt-br,pt;q=0.8,en-us;q=0.5,en;q=0.3\r\n
>Accept-Encoding: gzip,deflate\r\n
>Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7\r\n
>Keep-Alive: 300\r\n
>Connection: keep-alive\r\n
>Referer: http://penguin.wazollc.net:8080/at/\r\n
>Cookie: JSESSIONID=0AC67AD80A700A57714DA7E22BAFF574\r\n
>Content-Type: application/x-www-form-urlencoded\r\n
>Content-Length: 3437
>\r\n
> Line-based text data: application/x-www-form-urlencoded
>
_transaction=%3Ctransaction+xmlns%3Axsi%3D%22http%3A%2F%2Fwww.w3.org%2F2000%2F10%2FXMLSchema-instance%22+xsi%3Atype%3D%22xsd%3AObject%22%3E%3CtransactionNum+xsi%3Atype%3D%22xsd%3Along%22%3E0%3C%2FtransactionNum%3E%3Coperations+xsi%3Atype%3
>
> How do I send Line-based text data ? Do I need to set the headers Content-* ?
That's a bit clearer; I assume that "Line-based text data:
application/x-www-form-urlencoded" is a header added by Wireshark, so
the actual data is the stuff starting with:
_transaction=
This is a standard encoded POST message; all you need to do is to add
the appropriate parameters to the HTTP POST sampler.
In this case, the parameters are a bit tricky to determine, but
Wireshark may do it for you, or I found the following decoder page:
http://ostermiller.org/calc/encode.html
Or you can try using the HTTP Proxy recorder. Read the manual for details.
I'm all so close. Inside the code I didn't write we do:
public static boolean isRPC(HttpServletRequest httpservletrequest)
{
String s = httpservletrequest.getQueryString();
if(s == null)
return false;
else
return s.indexOf("is_isc_rpc=true") != -1;
}
Working httpservletrequest.getQueryString() from browser -->
is_isc_rpc=true&isc_clientVersion=5.6b2&iscTNum=0
From JMeter is null. I think this is because I put the ;jsession tag
on the url to associate the cookie:
POST
http://penguin.wazollc.net:8080/at/smartclient.form;jsessionid=C9981CC5C312D62EFED889AE5816A841
And passing the is_isc_rpc=true via a param. Hopefully this is the
last question - thanks for the help!
Robert
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: HTTPS: SSL instead of TLS
OK, I'm looking into enhancing the Socket factory code to try and fix this. S/// On 18/03/07, Steffen Oehme <[EMAIL PROTECTED]> wrote: I did some testing but it doesn't work: https.default.protocol=SSLv3 in user.properties JMeter picks this up correctly (as per jmeter.log) The WebLogic server still gives the TLS Error Message Don't you need to set the actual protocol with setEnabledProtocols of SSLSocket? Not familar with this, but from the API it seems as if this is the only way to specify exactly what protocol should be used. The getInstance of SSLContext that you used may not exclude TLS.. At least the description makes me believe so: SSL Supports some version of SSL; may support other versions SSLv2 Supports SSL version 2 or higher SSLv3 Supports SSL version 3; may support other versions TLS Supports some version of TLS; may support other versions TLSv1 Supports TLS version 1; may support other versions sebb schrieb: > https.default.protocol=TLS - 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]
Re: Adding condition for all Assertions ?
I've been thinking a bit more about this. To be able to use the existing "Logic Controllers" would be most powerful and elegant, since then you could also create loops, and check lots of assertions dynamically. But I'm afraid it might be quite complex to get that to work, because then you can have unlimited nesting of all elements in the test plan, I think. Currently that is avoided, since you cannot for example add "Logic Controllers" as a child to a Sampler. Does anybody know if it is possible currently to get "conditional Assertions" in a Test plan, i.e. where you can do an "if test on a user defined variable to check if the assertion should be executed" ? How does my idea about adding a condition field to all the Assertions sound ? Regards Alf Hogemark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HTTPS: SSL instead of TLS
I did some testing but it doesn't work: https.default.protocol=SSLv3 in user.properties JMeter picks this up correctly (as per jmeter.log) The WebLogic server still gives the TLS Error Message Don't you need to set the actual protocol with setEnabledProtocols of SSLSocket? Not familar with this, but from the API it seems as if this is the only way to specify exactly what protocol should be used. The getInstance of SSLContext that you used may not exclude TLS.. At least the description makes me believe so: SSL Supports some version of SSL; may support other versions SSLv2 Supports SSL version 2 or higher SSLv3 Supports SSL version 3; may support other versions TLS Supports some version of TLS; may support other versions TLSv1 Supports TLS version 1; may support other versions sebb schrieb: > https.default.protocol=TLS - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Baffled with cookie manager
On 18/03/07, robert lazarski <[EMAIL PROTECTED]> wrote: On 3/17/07, sebb <[EMAIL PROTECTED]> wrote: > > The above line is not a standard HTTP header - or is there a blank > line missing before it? Here's the entire request - after login - I'm capturing from wireshark run from the browser: Hypertext Transfer Protocol POST /at/smartclient.form?is_isc_rpc=true&isc_clientVersion=5.6b2&iscTNum=0 HTTP/1.1\r\n Request Method: POST Request URI: /at/smartclient.form?is_isc_rpc=true&isc_clientVersion=5.6b2&iscTNum=0 Request Version: HTTP/1.1 Host: penguin.wazollc.net:8080\r\n User-Agent: Mozilla/5.0 (X11; U; Linux i686; pt-BR; rv:1.8.1.2) Gecko/20070220 Firefox/2.0.0.2\r\n Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5\r\n Accept-Language: pt-br,pt;q=0.8,en-us;q=0.5,en;q=0.3\r\n Accept-Encoding: gzip,deflate\r\n Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7\r\n Keep-Alive: 300\r\n Connection: keep-alive\r\n Referer: http://penguin.wazollc.net:8080/at/\r\n Cookie: JSESSIONID=0AC67AD80A700A57714DA7E22BAFF574\r\n Content-Type: application/x-www-form-urlencoded\r\n Content-Length: 3437 \r\n Line-based text data: application/x-www-form-urlencoded _transaction=%3Ctransaction+xmlns%3Axsi%3D%22http%3A%2F%2Fwww.w3.org%2F2000%2F10%2FXMLSchema-instance%22+xsi%3Atype%3D%22xsd%3AObject%22%3E%3CtransactionNum+xsi%3Atype%3D%22xsd%3Along%22%3E0%3C%2FtransactionNum%3E%3Coperations+xsi%3Atype%3 How do I send Line-based text data ? Do I need to set the headers Content-* ? That's a bit clearer; I assume that "Line-based text data: application/x-www-form-urlencoded" is a header added by Wireshark, so the actual data is the stuff starting with: _transaction= This is a standard encoded POST message; all you need to do is to add the appropriate parameters to the HTTP POST sampler. In this case, the parameters are a bit tricky to determine, but Wireshark may do it for you, or I found the following decoder page: http://ostermiller.org/calc/encode.html Or you can try using the HTTP Proxy recorder. Read the manual for details. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Baffled with cookie manager
On 3/17/07, sebb <[EMAIL PROTECTED]> wrote: The above line is not a standard HTTP header - or is there a blank line missing before it? Here's the entire request - after login - I'm capturing from wireshark run from the browser: Hypertext Transfer Protocol POST /at/smartclient.form?is_isc_rpc=true&isc_clientVersion=5.6b2&iscTNum=0 HTTP/1.1\r\n Request Method: POST Request URI: /at/smartclient.form?is_isc_rpc=true&isc_clientVersion=5.6b2&iscTNum=0 Request Version: HTTP/1.1 Host: penguin.wazollc.net:8080\r\n User-Agent: Mozilla/5.0 (X11; U; Linux i686; pt-BR; rv:1.8.1.2) Gecko/20070220 Firefox/2.0.0.2\r\n Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5\r\n Accept-Language: pt-br,pt;q=0.8,en-us;q=0.5,en;q=0.3\r\n Accept-Encoding: gzip,deflate\r\n Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7\r\n Keep-Alive: 300\r\n Connection: keep-alive\r\n Referer: http://penguin.wazollc.net:8080/at/\r\n Cookie: JSESSIONID=0AC67AD80A700A57714DA7E22BAFF574\r\n Content-Type: application/x-www-form-urlencoded\r\n Content-Length: 3437 \r\n Line-based text data: application/x-www-form-urlencoded _transaction=%3Ctransaction+xmlns%3Axsi%3D%22http%3A%2F%2Fwww.w3.org%2F2000%2F10%2FXMLSchema-instance%22+xsi%3Atype%3D%22xsd%3AObject%22%3E%3CtransactionNum+xsi%3Atype%3D%22xsd%3Along%22%3E0%3C%2FtransactionNum%3E%3Coperations+xsi%3Atype%3 How do I send Line-based text data ? Do I need to set the headers Content-* ? Thanks! Robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HTTPS: SSL instead of TLS
Sorry, forgot to say what the property was... The default is: https.default.protocol=TLS I did not put it in jmeter.properties, because it may well be removed. S. On 18/03/07, Steffen Oehme <[EMAIL PROTECTED]> wrote: Sebb, what's the properties name and values again? Can't find it in the usual config files.. sebb schrieb: > I've uploaded r519437 if you want to try and break it ;-) - 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]
Re: HTTPS: SSL instead of TLS
Sebb, what's the properties name and values again? Can't find it in the usual config files.. sebb schrieb: > I've uploaded r519437 if you want to try and break it ;-) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
