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=xxxx > > 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]
