htt-users Mailing List for HTTP Test Tool
Brought to you by:
ia97lies
Menu
▾
▴
htt-users — htt user mail list
You can subscribe to this list here.
| 2012 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(6) |
May
(5) |
Jun
(2) |
Jul
(5) |
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Christian L. <li...@gm...> - 2013-07-02 19:57:23
|
Can you give me the version number? My latest code do have different stuff on the reported line. Just to be sure. And also can you check which OpenSSL Library you build against? Perhaps a too old one? Or a special rehl crafted one? Which was the last working httest version on your rehl? Regards Christian On 07/02/2013 07:42 PM, monkeycoder k6 wrote: > > ./configure --enable-lua-module > make > I get the following error > ssl_module.c: In function ‘ssl_tlsext_trace’: > ssl_module.c:248: error: ‘TLSEXT_TYPE_server_name’ undeclared (first > use in this function) > ssl_module.c:248: error: (Each undeclared identifier is reported only once > ssl_module.c:248: error: for each function it appears in.) > <mailto:htt...@li...> > thanks > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > > > _______________________________________________ > Htt-users mailing list > Htt...@li... > https://lists.sourceforge.net/lists/listinfo/htt-users |
|
From: monkeycoder k6 <mon...@gm...> - 2013-07-02 17:42:34
|
./configure --enable-lua-module make I get the following error ssl_module.c: In function ‘ssl_tlsext_trace’: ssl_module.c:248: error: ‘TLSEXT_TYPE_server_name’ undeclared (first use in this function) ssl_module.c:248: error: (Each undeclared identifier is reported only once ssl_module.c:248: error: for each function it appears in.) <htt...@li...> thanks <htt...@li...> |
|
From: Christian L. <li...@gm...> - 2013-06-04 10:11:40
|
Hi all The new version of the famos httest is uploaded to sourceforge. Binaries für Mac and Windows will follow. If you get the tar ball there is a scripts folder where you can find a way to use httest as a pentesting tool Regards Christian |
|
From: Christian L. <li...@gm...> - 2013-06-01 18:49:48
|
Hi all I found an error in the current 2.4.2 version along side of my logger overwork. The command _DEBUG do not print anything at all. If somebody depends on that use 2.3.x versions until the next 2.4.3 release, it is then fixed promise (a test is now in place, should not happen anymore). Regards Christian |
|
From: Christian L. <li...@gm...> - 2012-11-13 20:41:15
|
On 11/13/2012 04:33 PM, Dossy Shiobara wrote: > On 11/13/12 2:41 AM, Christian Liesch wrote: >> Thanks very much. No currently there is no defined process for httest >> development. If you have a usefull patch feel free to send me that. The >> module concept in httest makes it relativly easy to add new >> functionality blocks :) > Excellent. I'll take a look into it. I'll also probably look at > integrating Tcl which should be fairly easy if Lua's already supported. I'm lookin forward for a tcl_module.c ;) But it was not that easy to integrate lua into httest and it is, in my opinion, not very well done. But perhaps you get a clue if you look into lua_module.c and configure.in. I think loading Modules at runtime would be nice to enable even user specific modules. But attention httest 3 do break with many "old" things... > >> I think many stuff you want have is allready there: >> >> * shared variables >> ... >> * Init blocks could be done this way > The variables are shared across threads? Perfect. Yes. > > In the user-guide.pdf for 2.2.11, I don't see mention of the "GLOBAL" > keyword. Is that only in the dev 3.x code, or is that in 2.2.11 and not > documented in the user guide? Hmmm yes I forgot that, I'm a lazy document writer :( > Using a CLIENT/GO combo to implement the init block is a clever idea. > I'll give that a try. GO is an old command designed for a shell mode I abuse for joining all CLIENT/SERVER not DAEMON. > I'm not sure if I'm interpreting the behavior correctly, but in a script > that contains both a CLIENT and DAEMON block, it seems like the FINALLY > block is being executed when the DAEMON block terminates, even though > the CLIENT block is still executing? I was under the impression that > the FINALLY block should only evaluate when _all_ CLIENT/SERVER/DAEMON > blocks terminate? Not good if that is realy true, I have to test this and fix this. The finally should be called after all CLIENT/SERVER are terminated, no mather if there is DAEMON still running. A DAEMON is a independant thread, which could for example be used to limit a test duration. For example DAEMON _SLEEP 60000 _DEBUG test duration too long _EXIT FAILED END But if there is no _EXIT the httest do run as long as there is a CLIENT/SERVER running... > I suppose I should start reading the test suite and the source and not > solely rely on the user-guide (which is fantastic, by the way). Thanks > for the tips! > Welcome |
|
From: Dossy S. <do...@pa...> - 2012-11-13 15:33:41
|
On 11/13/12 2:41 AM, Christian Liesch wrote: > Thanks very much. No currently there is no defined process for httest > development. If you have a usefull patch feel free to send me that. The > module concept in httest makes it relativly easy to add new > functionality blocks :) Excellent. I'll take a look into it. I'll also probably look at integrating Tcl which should be fairly easy if Lua's already supported. > I think many stuff you want have is allready there: > > * shared variables > ... > * Init blocks could be done this way The variables are shared across threads? Perfect. In the user-guide.pdf for 2.2.11, I don't see mention of the "GLOBAL" keyword. Is that only in the dev 3.x code, or is that in 2.2.11 and not documented in the user guide? Using a CLIENT/GO combo to implement the init block is a clever idea. I'll give that a try. I'm not sure if I'm interpreting the behavior correctly, but in a script that contains both a CLIENT and DAEMON block, it seems like the FINALLY block is being executed when the DAEMON block terminates, even though the CLIENT block is still executing? I was under the impression that the FINALLY block should only evaluate when _all_ CLIENT/SERVER/DAEMON blocks terminate? I suppose I should start reading the test suite and the source and not solely rely on the user-guide (which is fantastic, by the way). Thanks for the tips! -- Dossy Shiobara | "He realized the fastest way to change do...@pa... | is to laugh at your own folly -- then you http://panoptic.com/ | can let go and quickly move on." (p. 70) * WordPress * jQuery * MySQL * Security * Business Continuity * |
|
From: Christian L. <li...@gm...> - 2012-11-13 07:41:33
|
Hi Dossy
Thanks very much. No currently there is no defined process for httest
development. If you have a usefull patch feel free to send me that. The
module concept in httest makes it relativly easy to add new
functionality blocks :)
I currently up work the syntax and make it more flexible, would be
httest 3.x. But I do not have plans when to launch it and how to
read/migrate old scripts.
I think many stuff you want have is allready there:
* shared variables
GLOBAL yourVar yourVar2
GLOBAL yourVar3
CLIENT
_SET yourVar=foo
END
CLIENT
_SLEEP 1000
_DEBUG $yourVar
END
* Init blocks could be done this way
CLIENT
# do what ever you need to start with your tests
END
GO
#now start your tests
CLIENT
...
END
* Performance Tests:
I think httest is not the fastest on the market, needs a lot CPU power :(
But with the
PERF:DISTRIBUTED <host>:<port>
PERF:RAMPUP <clients> per <interval>
you could even distribute and ramup your clients (Rampup even works
distributed). But it is a little quricky this distributed thing. Please
have a look into the test folder within the tar ball. You will find
there many examples how a command could be use, just grep the command ;)
I hope that helps.
Best regards
Christian
On 11/13/12 05:37, Dossy Shiobara wrote:
> Hi,
>
> I just discovered httest today, and like what I see so far. Simple
> concurrency primitives, simple syntax, compiled executable: all huge
> plusses.
>
> The FINALLY block is useful. Could an INIT block be similarly defined
> that gets executed at the start?
>
> It appears that variables are not thread-shared. There's PROC:LOCK and
> PROC:UNLOCK, but no IPC mechanism to pass data between threads. That's
> unfortunate.
>
> I'm looking to use httest for benchmarking and load testing. At the
> minimum, having an INIT block implemented would be helpful for executing
> stuff before testing starts (set up test, etc.).
>
> What's the development process like for httest? Is there a patch
> submission process?
>
> Thanks for all the great work,
>
> Dossy
>
|
|
From: Dossy S. <do...@pa...> - 2012-11-13 05:04:09
|
Hi, I just discovered httest today, and like what I see so far. Simple concurrency primitives, simple syntax, compiled executable: all huge plusses. The FINALLY block is useful. Could an INIT block be similarly defined that gets executed at the start? It appears that variables are not thread-shared. There's PROC:LOCK and PROC:UNLOCK, but no IPC mechanism to pass data between threads. That's unfortunate. I'm looking to use httest for benchmarking and load testing. At the minimum, having an INIT block implemented would be helpful for executing stuff before testing starts (set up test, etc.). What's the development process like for httest? Is there a patch submission process? Thanks for all the great work, Dossy -- Dossy Shiobara | "He realized the fastest way to change do...@pa... | is to laugh at your own folly -- then you http://panoptic.com/ | can let go and quickly move on." (p. 70) * WordPress * jQuery * MySQL * Security * Business Continuity * |
|
From: Christian L. <li...@gm...> - 2012-07-23 08:10:59
|
Revision *1.1* - (view <http://htt.cvs.sourceforge.net/viewvc/htt/httest/src/httest.c?revision=1.1&view=markup>) (download <http://htt.cvs.sourceforge.net/viewvc/htt/httest/src/httest.c?revision=1.1>) (as text <http://htt.cvs.sourceforge.net/viewvc/htt/httest/src/httest.c?revision=1.1&content-type=text%2Fplain>) (annotate <http://htt.cvs.sourceforge.net/viewvc/htt/httest/src/httest.c?annotate=1.1>) - [select for diffs] <http://htt.cvs.sourceforge.net/viewvc/htt/httest/src/httest.c?r1=1.1&view=log> /Mon Jul 23 11:04:38 2007 UTC/ (5 years ago) by /ia97lies/ Branch: *MAIN* <http://htt.cvs.sourceforge.net/viewvc/htt/httest/src/httest.c?view=log&pathrev=MAIN> Branch point for: *ia97lies* <http://htt.cvs.sourceforge.net/viewvc/htt/httest/src/httest.c?view=log&pathrev=ia97lies> Initial revision |
|
From: Christian L. <li...@gm...> - 2012-07-19 05:54:05
|
Another aproach would be remove the odd "_" and use lower case letters.
This would look like that.
client
req localhost 8080
__GET / HTTP/1.1
__Host: localhost:8080
__
expect . "foo"
wait
end
And a migration script would be easy to write. Even adjust the
documentation could be done automaticaly. More ideas?
--
Christian
On 07/18/12 12:50, Christian Liesch wrote:
> I think about an new major release for httest with signifcant syntax
> changes. But still not sure how to do this. Here is a sample it could
> look like:
>
> CLIENT
> store = {}
> function foo(a)
> end
>
> function bla(c)
> end
>
> foo("hallo")
> bla("heho")
>
> auto_close(true)
>
> connect(
> "https://127.0.0.1:8080",
> ssl:set_cert("foo.cert.pem", "foo.key.pem", "foo.ca.pem")
> )
>
> __GET / HTTP/1.1
> __Host: localhost:8080
> __
> expect(body, "foo")
> match(header, "Set-Cookie: mycookie=([^;]+)" cookie)
> wait()
>
> bps(200, function()
> __GET / HTTP/1.1
> __Host: localhost:8080
> __Cookie: mycookie=$cookie
> __
> wait()
> end)
>
> for i=1,10 do
> __GET / HTTP/1.1
> __Host: localhost:8080
> __
> expect(body, "foo");
> wait()
> end
> END
>
> But this looks not that readable as the old syntax. It is a mixup of
> lua and httest syntax. The only command I would make with httest would
> be __ and _-. Then I need a compilation step to embedd this httest
> commands to lua.
>
> Any other suggestions?
>
> Thanks
> Christian
|
|
From: Christian L. <li...@gm...> - 2012-07-18 10:54:01
|
I think about an new major release for httest with signifcant syntax
changes. But still not sure how to do this. Here is a sample it could
look like:
CLIENT
store = {}
function foo(a)
end
function bla(c)
end
foo("hallo")
bla("heho")
auto_close(true)
connect(
"https://127.0.0.1:8080",
ssl:set_cert("foo.cert.pem", "foo.key.pem", "foo.ca.pem")
)
__GET / HTTP/1.1
__Host: localhost:8080
__
expect(body, "foo")
match(header, "Set-Cookie: mycookie=([^;]+)" cookie)
wait()
bps(200, function()
__GET / HTTP/1.1
__Host: localhost:8080
__Cookie: mycookie=$cookie
__
wait()
end)
for i=1,10 do
__GET / HTTP/1.1
__Host: localhost:8080
__
expect(body, "foo");
wait()
end
END
But this looks not that readable as the old syntax. It is a mixup of lua
and httest syntax. The only command I would make with httest would be __
and _-. Then I need a compilation step to embedd this httest commands to
lua.
Any other suggestions?
Thanks
Christian
|
|
From: Cyril S. <cyr...@gm...> - 2012-07-04 14:52:19
|
Thanks, I solve my problem. I didn't add "_auto_close on", I want to make several request in one tcp connections. But, I fix the configuration of my http server. The keep-alive was disable. Sorry. Cyril On Wed, Jul 4, 2012 at 10:02 AM, Christian Liesch <li...@gm...> wrote: > Hi > > I think it is a just luck that this script do not fail :) Httest do nothing > or nearly nothing automatic expcept it is told to. I think this is a > keep-alive issue. If this is not what you want to test you have to add the > following line right after CLIENT: > > _AUTO_CLOSE on > > Now httest do handle "Connection: close" from the server. If the server do > close connection without telling this with "Connection: close" header this > test will fail again. > > If this do not help, please send the complete output of your script. > > And the line numbers of the error is not correct too?! Is this realy the > hole script or just a snipplet? > > Regards > Christian > > > On 07/04/2012 03:41 PM, Cyril SANTUNE wrote: >> >> Hi, >> >> I don't understand why this test failed. >> --- >> CLIENT >> # Open tcp connection >> _REQ 10.68.40.1 80 >> #_SLEEP 5000 >> __GET /read/4KB.txt HTTP/1.1 >> __Host: 10.68.40.1 >> __ >> # We expect a 200 OK from the server >> # and we also expect Response data send from server >> # If we get something different the script will fail >> _EXPECT . "HTTP/1.1 200 OK" >> #_EXPECT . "Server 10.68.40.1" >> _WAIT >> _REQ 10.68.40.1 80 >> #_SLEEP 5000 >> __GET /read/4KB.txt HTTP/1.1 >> __Host: 10.68.40.1 >> __ >> _EXPECT . "HTTP/1.1 200 OK" >> _WAIT >> END >> --- >> >> I obtain this error: >> --- >> test_client.htt:41: error: CLT0-0 End of file found(70014) >> >> test_client.htt:25: error: CLT0-0 End of file found(70014) >> FAILED >> --- >> >> This test work with an other computer with the same OS (Windows XP). >> >> I have no problem with this test: >> --- >> CLIENT >> # Open tcp connection >> _REQ 10.68.40.1 80 >> #_SLEEP 5000 >> __GET /read/4KB.txt HTTP/1.1 >> __Host: 10.68.40.1 >> __ >> # We expect a 200 OK from the server >> # and we also expect Response data send from server >> # If we get something different the script will fail >> _EXPECT . "HTTP/1.1 200 OK" >> #_EXPECT . "Server 10.68.40.1" >> _WAIT >> END >> --- >> >> I am on Windows XP SP2 with microsoft c++ 2005 and 2008 >> >> Any idea ? >> >> Thanks, >> Cyril >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Htt-users mailing list >> Htt...@li... >> https://lists.sourceforge.net/lists/listinfo/htt-users > > > |
|
From: Cyril S. <cyr...@gm...> - 2012-07-04 13:42:02
|
Hi,
I don't understand why this test failed.
---
CLIENT
# Open tcp connection
_REQ 10.68.40.1 80
#_SLEEP 5000
__GET /read/4KB.txt HTTP/1.1
__Host: 10.68.40.1
__
# We expect a 200 OK from the server
# and we also expect Response data send from server
# If we get something different the script will fail
_EXPECT . "HTTP/1.1 200 OK"
#_EXPECT . "Server 10.68.40.1"
_WAIT
_REQ 10.68.40.1 80
#_SLEEP 5000
__GET /read/4KB.txt HTTP/1.1
__Host: 10.68.40.1
__
_EXPECT . "HTTP/1.1 200 OK"
_WAIT
END
---
I obtain this error:
---
test_client.htt:41: error: CLT0-0 End of file found(70014)
test_client.htt:25: error: CLT0-0 End of file found(70014)
FAILED
---
This test work with an other computer with the same OS (Windows XP).
I have no problem with this test:
---
CLIENT
# Open tcp connection
_REQ 10.68.40.1 80
#_SLEEP 5000
__GET /read/4KB.txt HTTP/1.1
__Host: 10.68.40.1
__
# We expect a 200 OK from the server
# and we also expect Response data send from server
# If we get something different the script will fail
_EXPECT . "HTTP/1.1 200 OK"
#_EXPECT . "Server 10.68.40.1"
_WAIT
END
---
I am on Windows XP SP2 with microsoft c++ 2005 and 2008
Any idea ?
Thanks,
Cyril
|
|
From: Christian L. <li...@gm...> - 2012-06-06 12:35:00
|
New with performance testing support. To distribute your CLIENTs to hosts you have to specify these remote hosts with PERF:DISTRIBUTE <host>:<port> PERF:DISTRIBUTE <host2>:<port2> ... And on the single <host>:<port>, <host2>:<port2>, ... you have to start an httest angent <host>: htremote -r -p <port> -e "<path-to-htest>/httest -Ssn" <host2>: htremote -r -p <port> -e "<path-to-httest>/httest -Ssn" ... If the host is not available it will skip that host. Have fun :) |
|
From: Christian L. <li...@gm...> - 2012-06-01 08:39:12
|
httest 2.1 serie is no longer supported. Use the httest 2.2 instead. |
|
From: Christian L. <li...@gm...> - 2012-05-29 21:33:20
|
Bugfix possible segfault in _SSL:TRACE command. |
|
From: Christian L. <li...@gm...> - 2012-05-25 13:39:24
|
httest do now work with openssl 1.0.1, tested with the latest openssl version 1.0.1c have lot of fun... |
|
From: ZHANG L. <Lin...@al...> - 2012-05-02 08:51:37
|
Dear Christian, Thanks for your rapid response! I will register user account to posting. And my problem has been resolved. Bests! ________________________________ From: Christian Liesch [mailto:li...@gm...] Sent: 2012年5月2日星期三 16:39 To: ZHANG Lingli Cc: htt...@li... Subject: Re: [Htt-users] htt tool Hi Lingli Two Things. First: Please do not post your questions to both htt groups. Questions about the Code must be send to developers list. Questions to scripts/commands to the users list. Second: Please register yourself to the users list before posting. Else I have to aprove your posting first in the users list admin page everytime. To your Question: The Things you EXPECT are not fullfilled. Perhaps you got not a "200 OK"? Or the "zll" is not in the answer? For more help, please post all Output. Regards. On 05/02/12 10:02, ZHANG Lingli wrote: Dear htt, With the command "./httest tmsd.htt",then return the following error :tmsd.htt:8: error: CLT0-0 Invalid argument(22) . The following is tmsd.htt contents: CLIENT _REQ 135.251.208.116 8080 __POST /tmsd/userLogin.do HTTP/1.1 __Host:135.251.208.116 __ _EXPECT . "200 OK" _EXPECT . "zll" _WAIT END Where is wrong? Thanks! Lingli ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Htt-users mailing list Htt...@li...<mailto:Htt...@li...> https://lists.sourceforge.net/lists/listinfo/htt-users |
|
From: Christian L. <li...@gm...> - 2012-05-02 08:39:09
|
Hi Lingli Two Things. First: Please do not post your questions to both htt groups. Questions about the Code must be send to developers list. Questions to scripts/commands to the users list. Second: Please register yourself to the users list before posting. Else I have to aprove your posting first in the users list admin page everytime. To your Question: The Things you EXPECT are not fullfilled. Perhaps you got not a "200 OK"? Or the "zll" is not in the answer? For more help, please post all Output. Regards. On 05/02/12 10:02, ZHANG Lingli wrote: > Dear htt, > With the command "./httest tmsd.htt",then return the following error > :tmsd.htt:8: error: CLT0-0 Invalid argument(22) . > The following is tmsd.htt contents: > CLIENT > _REQ 135.251.208.116 8080 > __POST /tmsd/userLogin.do HTTP/1.1 > __Host:135.251.208.116 > __ > _EXPECT . "200 OK" > _EXPECT . "zll" > _WAIT > END > Where is wrong? > Thanks! > Lingli > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > > _______________________________________________ > Htt-users mailing list > Htt...@li... > https://lists.sourceforge.net/lists/listinfo/htt-users |
|
From: ZHANG L. <Lin...@al...> - 2012-05-02 08:18:10
|
Dear htt, With the command "./httest tmsd.htt",then return the following error :tmsd.htt:8: error: CLT0-0 Invalid argument(22) . The following is tmsd.htt contents: CLIENT _REQ 135.251.208.116 8080 __POST /tmsd/userLogin.do HTTP/1.1 __Host:135.251.208.116 __ _EXPECT . "200 OK" _EXPECT . "zll" _WAIT END Where is wrong? Thanks! Lingli |
|
From: Christian L. <li...@gm...> - 2012-04-26 07:17:44
|
Hi Bleeding edge httest can now wait for started threads befor start new threads, with the old "GO" command. I fixed this command. Now the following is working properly: CLIENT ... END GO CLIENT ... END CLIENT ... END SERVER 8080 ... END Attention SERVER/CLIENT/DAEMON are threads. This example starts the first CLIENT before starting the rest of the script even the SERVER! Best regards |
|
From: Christian L. <li...@gm...> - 2012-04-24 06:38:51
|
New Release 2.2.2 is out now. There are 2 new commands: * _SSL:TRACE This command turns on SSL message tracing: All SSL messages are visible and the commands _EXPECT/_MATCH/_GREP do work in the namespace "." and "headers" Example: CLIENT _SSL:TRACE _REQ foo.bar.ch SSL:443 __GET / HTTP/1.1 __Host: foo.bar.ch __ _EXPECT headers "ClientHello" _WAIT ... END * _SSL:SET_CIPHER_SUITE See here how to build a cipher suite list string: http://www.openssl.org/docs/apps/ciphers.html#CIPHER_LIST_FORMAT Have fun |
|
From: Christian L. <li...@gm...> - 2012-04-17 20:55:22
|
On 04/17/2012 10:51 PM, Christian Liesch wrote: > New Release with simple javascript support and XPath support. > > See in $TOP/test/block_js*.htt and $TOP/test/html.htt for example how to > use the new features. > > Have lots of fun :) > > > ------------------------------------------------------------------------------ > Better than sec? Nothing is better than sec when it comes to > monitoring Big Data applications. Try Boundary one-second > resolution app monitoring today. Free. > http://p.sf.net/sfu/Boundary-dev2dev > _______________________________________________ > Htt-users mailing list > Htt...@li... > https://lists.sourceforge.net/lists/listinfo/htt-users I forgot the new command GLOBAL to define variable used globaly and are shared among the threads GLOBAL myShared1 myShared2 CLIENT _SET myShared1=foo _REQ localhost 8080 __GET / HTTP/1.1 __Host: localhost __ _MATCH headers "Set-Cookie: ([^;]+)" myShared2 _WAIT END CLIENT _SLEEP 1000 _DEBUG $myShared1 _DEBUG $myShared2 END |
|
From: Christian L. <li...@gm...> - 2012-04-17 20:51:16
|
New Release with simple javascript support and XPath support. See in $TOP/test/block_js*.htt and $TOP/test/html.htt for example how to use the new features. Have lots of fun :) |
|
From: Christian L. <li...@gm...> - 2012-04-06 22:29:55
|
Hi All The first version 2.2.0 of the new 2.2 series of httest is available. http://sourceforge.net/projects/htt/files/htt2.2/ You need to download spidermonkey from Mozilla and build/install it, before you can enable the js support. https://developer.mozilla.org/en/SpiderMonkey The javascript support is rudimentary with no much functionality at all. This is just the start for the next generation of httest with many support around HTML and javascript. Have fun |
