/*
 
  Connecting to www.mail.ru over TCP, then sends the HTTP request
 
  run program as
      anettest -T 5000 -d client:www.mail.ru:80 -f send_http_message.fws
 
  under UNIX you should not delete CR (^M) symboles from this file or you should add them (\r)
 
  you may watch the result with some sniffer
 
 */

DEVICE   PARAMETERS: <type of DEVICE   PARAMETERS: <type of DEVICE   PARAMETERS: <type of device> {<name of interface>}
Reopens interfaces. The type of device: eth, ip, tcp. The name of device is the same as for -d option, depends on the type of device. New line terminates the list of names.

> {<name of interface>}
Reopens interfaces. The type of device: eth, ip, tcp. The name of device is the same as for -d option, depends on the type of DEVICE   PARAMETERS: <type of device> {<name of interface>}
Reopens interfaces. The type of device: eth, ip, tcp. The name of device is the same as for -d option, depends on the type of device. New line terminates the list of names.

. New line terminates the list of names.

> {<name of interface>}
Reopens interfaces. The type of device: eth, ip, tcp. The name of device is the same as for -d option, depends on the type of DEVICE   PARAMETERS: <type of DEVICE   PARAMETERS: <type of device> {<name of interface>}
Reopens interfaces. The type of device: eth, ip, tcp. The name of device is the same as for -d option, depends on the type of device. New line terminates the list of names.

> {<name of interface>}
Reopens interfaces. The type of device: eth, ip, tcp. The name of device is the same as for -d option, depends on the type of DEVICE   PARAMETERS: <type of device> {<name of interface>}
Reopens interfaces. The type of device: eth, ip, tcp. The name of device is the same as for -d option, depends on the type of device. New line terminates the list of names.

. New line terminates the list of names.

. New line terminates the list of names.

 tcp "client:www.mail.ru:80"

NEWLINEIS   PARAMETERS: <string>
Sets the string which must replace any original LF symbol while working with strings. See "samples/strings.fws"

 '\r\n'

data
"GET / HTTP/1.1
User-Agent: Opera/9.00 (Windows NT 5.1; U; en)
Host: www.mail.ru
ACCEPT   PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of SEND   PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST   PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/FASTTEST   PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

".

 and option -c) may simply separate packets one from another, so by this command the current content of buffer will be fixed and the new packet will be registered. The requests after command don't make sense in common regime (only while testing packet filter).

 ACCEPT   PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of SEND   PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST   PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

 and option -c) may simply separate packets one from another, so by this command the current content of buffer will be fixed and the new packet will be registered. The requests after command don't make sense in common regime (only while testing packet filter).

 ACCEPT   PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of SEND   PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST and option -c) may simply separate packets one from another, so by this command the current content of buffer will be fixed and the new packet will be registered. The requests after command don't make sense in common regime (only while testing packet filter).

 ACCEPT   PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of SEND ACCEPT. It may be processed as command while testing packet filter only (command FASTTEST or option -c). In common regime it may be among parameters to command only.

. It may be processed as command while testing packet filter only (command FASTTEST   PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

 or option -c). In common regime it may be among parameters to command only.

. It may be processed as command while testing packet filter only (command FASTTEST   PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/FASTTEST   PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

".

 or option -c). In common regime it may be among parameters to command only.

. It may be processed as command while testing packet filter only (command FASTTEST   PARAMETERS: no parameters
Enables FASTTEST   PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

 regime for packet filter test. See "samples/FASTTEST   PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/FASTTEST   PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

".

".

 or option -c). In common regime it may be among parameters to command only.

-Language: ru_RU,ru;q=0.9,en;q=0.8
ACCEPT   PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of SEND   PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST   PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/FASTTEST   PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

".

 and option -c) may simply separate packets one from another, so by this command the current content of buffer will be fixed and the new packet will be registered. The requests after command don't make sense in common regime (only while testing packet filter).

 ACCEPT   PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of SEND   PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST   PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

 and option -c) may simply separate packets one from another, so by this command the current content of buffer will be fixed and the new packet will be registered. The requests after command don't make sense in common regime (only while testing packet filter).

 ACCEPT   PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of SEND   PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST and option -c) may simply separate packets one from another, so by this command the current content of buffer will be fixed and the new packet will be registered. The requests after command don't make sense in common regime (only while testing packet filter).

 ACCEPT   PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of SEND ACCEPT. It may be processed as command while testing packet filter only (command FASTTEST or option -c). In common regime it may be among parameters to command only.

. It may be processed as command while testing packet filter only (command FASTTEST   PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

 or option -c). In common regime it may be among parameters to command only.

. It may be processed as command while testing packet filter only (command FASTTEST   PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/FASTTEST   PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

".

 or option -c). In common regime it may be among parameters to command only.

. It may be processed as command while testing packet filter only (command FASTTEST   PARAMETERS: no parameters
Enables FASTTEST   PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

 regime for packet filter test. See "samples/FASTTEST   PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/FASTTEST   PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

".

".

 or option -c). In common regime it may be among parameters to command only.

-Charset: iso-8859-1
RANGE   PARAMETERS: <number of start packet> <number of stop packet>
While imitation of application's work the work will be performed with packets (from trace file) which are within the given RANGE   PARAMETERS: <number of start packet> <number of stop packet>
While imitation of application's work the work will be performed with packets (from trace file) which are within the given RANGE   PARAMETERS: <number of start packet> <number of stop packet>
While imitation of application's work the work will be performed with packets (from trace file) which are within the given range. Null value for start packet means first packet in file. Null value for stop packet means last packet in file.

. Null value for start packet means first packet in file. Null value for stop packet means last packet in file.

. Null value for start packet means first packet in file. Null value for stop packet means last packet in file.

: bytes=45-46
Connection: Keep-Alive

"

 //Accept: text/html, application/xml;q=0.9, application/xhtml+xml, image/png, image/jpeg, image/gif, image/x-xbitmap, */*;q=0.1
 //Accept-Encoding: deflate, x-gzip, identity, *;q=0
 //Cookie: mrcu=4C1043752F867C83F61EF6965850; p=RRoAAULPXgAA; p_sid=b03e2abtd5fe3ef941244099583a0dcc; c0=pIemRQYAAADtAAIAAAAAAO2gAQAAAAAA; b15719=undefined; MailUser=1; Mpop=1166752409:7d62525b4675527d19050219091d011b0a024f6c5150445e040504031b01067b1f5043564c4806026e06145a545858194b44:group72_1@mail.ru:; t=obLD1UAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAATAAAAAAAAAABAAABAAAAAAAAAAAAAATJ0gcA; mrcu=4C1043752F867C83F61EF6345850
 //Cookie2: $Version=1
 // Accept-Charset: iso-8859-1, utf-8, utf-16, *;q=0.1
 
             SEND   PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST   PARAMETERS: no parameters
Enables FASTTEST   PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

 regime for packet filter test. See "samples/FASTTEST   PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/FASTTEST   PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

".

".

 and option -c) may simply separate packets one from another, so by this command the current content of buffer will be fixed and the new packet will be registered. The requests after command don't make sense in common regime (only while testing packet filter).

       // sending data
             PAUSE   PARAMETERS: <number of milliseconds>
Pauses the execution for a specified interval of time.

 5000 // PAUSE   PARAMETERS: <number of milliseconds>
Pauses the execution for a specified interval of time.

 befor closing connection