Gateway.exe infinite loop

[Damien Bonvillain]

Hello,
I write here before opening a bug in order to get some input.
Here is the configuration:
- OpenSTA 1.4.4.11
- Windows XP SP2
- Browser IE7 and Firefox (same behaviour)

While recording a script:
- gateway listening on 192.168.1.103:81
- target server is 192.168.1.103:8033 (same machine)
- fetching the very first URL (IE or Firefox address bar + <enter>),
gateway.exe goes 100% on the CPU, and opens a load connexions.

Here is the begininning of the console:
Running in default mode (as a console)...


Initialize the gateway...
Listening on < 192.168.1.103:3000>.
Gateway is running...
Connection from <192.168.1.103:2759>.
Listening default on <192.168.1.103:81 > for <> using gwhttp.dll.

Original Browser configuration
------------------------------
Proxy Configuration : HTTP:POROP103:81;SSL:POROP103:81;FTP:POROP103:81;GOPHER:PO
ROP103:81;SOCKS:POROP103:81
Exceptions :
Local Proxy Value : proxy_for_local

Connection from <192.168.1.103:2761> to default <0.0.0.0:0> using gwhttp.dll .
Connection from <192.168.1.103:2762> to default <0.0.0.0:0> using gwhttp.dll.
Connection from < 192.168.1.103:2763> to default <0.0.0.0:0> using gwhttp.dll.
Connection from <192.168.1.103:2764> to default < 0.0.0.0:0> using gwhttp.dll.
Connection from <192.168.1.103:2765> to default <0.0.0.0:0> using gwhttp.dll.
Connection from < 192.168.1.103:2766> to default <0.0.0.0:0> using gwhttp.dll.
[... the port number is sequentially incremented]
Connection from < 192.168.1.103:2804> to default <0.0.0.0:0> using gwhttp.dll.
Connection from <192.168.1.103:2805> to default < 0.0.0.0:0> using gwhttp.dll.
Connection from <192.168.1.103:2806> to default <0.0.0.0:0> using gwhttp.dll.
Connection from < 192.168.1.103:2807> to default <0.0.0.0:0> using gwhttp.dll.


Activating Console & Trace (same bloc repeated over and over):
 > ACT 3: SELECT:CAPTURE> ACT 3: SELECT:CAPTURE.
>>> GCT 5: new gateway client task.
>>> GCT 5: try to load the library 'gwhttp.dll'.
>>> GCT 5: <application client    -> ' gwhttp.dl' -> target listener      >
>>> GCT 5: <192.168.1.103:3109    -> 81/0        -> 0.0.0.0:0            >
>>> GCT 5: target address auto detect mode is actif.
nspsend:packet dump - parseBuffer 1,350
nspsend:47 45 54 20 68 74 74 70 3A 2F 2F 31 39 32 2E 31 36 38 2E 31 2E
31 30 33 3A 38 30 33 33 2F 20 48  |GET http://192.168.1.103:8033/ H|
nspsend:54 54 50 2F 31 2E 31 0D 0A 41 63 63 65 70 74 3A 20 2A 2F 2A 0D
0A 41 63 63 65 70 74 2D 4C 61 6E  |TTP/1.1..Accept: */*..Accept-Lan|
nspsend:67 75 61 67 65 3A 20 66 72 0D 0A 55 41 2D 43 50 55 3A 20 78 38
36 0D 0A 41 63 63 65 70 74 2D 45  |guage: fr..UA-CPU: x86..Accept-E|
nspsend:6E 63 6F 64 69 6E 67 3A 20 67 7A 69 70 2C 20 64 65 66 6C 61 74
65 0D 0A 55 73 65 72 2D 41 67 65  |ncoding: gzip, deflate..User-Age|
nspsend:6E 74 3A 20 4D 6F 7A 69 6C 6C 61 2F 34 2E 30 20 28 63 6F 6D 70
61 74 69 62 6C 65 3B 20 4D 53 49  |nt: Mozilla/4.0 (compatible; MSI|
nspsend:45 20 37 2E 30 3B 20 57 69 6E 64 6F 77 73 20 4E 54 20 35 2E 31
3B 20 28 52 31 20 31 2E 36 29 3B  |E 7.0; Windows NT 5.1; (R1 1.6);|
nspsend:20 2E 4E 45 54 20 43 4C 52 20 31 2E 31 2E 34 33 32 32 3B 20 49
6E 66 6F 50 61 74 68 2E 32 3B 20  | .NET CLR 1.1.4322; InfoPath.2; |
nspsend:2E 4E 45 54 20 43 4C 52 20 32 2E 30 2E 35 30 37 32 37 3B 20 2E
4E 45 54 20 43 4C 52 20 33 2E 30  |.NET CLR 2.0.50727; .NET CLR 3.0|
nspsend:2E 30 34 35 30 36 2E 33 30 3B 20 2E 4E 45 54 20 43 4C 52 20 33
2E 30 2E 30 34 35 30 36 2E 36 34  |.04506.30; .NET CLR 3.0.04506.64|
nspsend:38 29 0D 0A 48 6F 73 74 3A 20 31 39 32 2E 31 36 38 2E 31 2E 31
30 33 3A 38 30 33 33 0D 0A 50 72  |8)..Host: 192.168.1.103:8033..Pr|
nspsend:6F 78 79 2D 43 6F 6E 6E 65 63 74 69 6F 6E 3A 20 4B 65 65 70 2D
41 6C 69 76 65 0D 0A 0D 0A 00 00  |oxy-Connection: Keep-Alive......|
After
nspsend:47 45 54 20 68 74 74 70 3A 2F 2F 31 39 32 2E 31 36 38 2E 31 2E
31 30 33 3A 38 30 33 33 2F 20 48  |GET http://192.168.1.103:8033/ H|
nspsend:54 54 50 2F 31 2E 31 0D 0A 41 63 63 65 70 74 3A 20 2A 2F 2A 0D
0A 41 63 63 65 70 74 2D 4C 61 6E  |TTP/1.1..Accept: */*..Accept-Lan|
nspsend:67 75 61 67 65 3A 20 66 72 0D 0A 55 41 2D 43 50 55 3A 20 78 38
36 0D 0A 41 63 63 65 70 74 2D 45  |guage: fr..UA-CPU: x86..Accept-E|
nspsend:6E 63 6F 64 69 6E 67 3A 20 67 7A 69 70 2C 20 64 65 66 6C 61 74
65 0D 0A 55 73 65 72 2D 41 67 65  |ncoding: gzip, deflate..User-Age|
nspsend:6E 74 3A 20 4D 6F 7A 69 6C 6C 61 2F 34 2E 30 20 28 63 6F 6D 70
61 74 69 62 6C 65 3B 20 4D 53 49  |nt: Mozilla/4.0 (compatible; MSI|
nspsend:45 20 37 2E 30 3B 20 57 69 6E 64 6F 77 73 20 4E 54 20 35 2E 31
3B 20 28 52 31 20 31 2E 36 29 3B  |E 7.0; Windows NT 5.1; (R1 1.6);|
nspsend:20 2E 4E 45 54 20 43 4C 52 20 31 2E 31 2E 34 33 32 32 3B 20 49
6E 66 6F 50 61 74 68 2E 32 3B 20  | .NET CLR 1.1.4322; InfoPath.2; |
nspsend:2E 4E 45 54 20 43 4C 52 20 32 2E 30 2E 35 30 37 32 37 3B 20 2E
4E 45 54 20 43 4C 52 20 33 2E 30  |.NET CLR 2.0.50727; .NET CLR 3.0|
nspsend:2E 30 34 35 30 36 2E 33 30 3B 20 2E 4E 45 54 20 43 4C 52 20 33
2E 30 2E 30 34 35 30 36 2E 36 34  |.04506.30; .NET CLR 3.0.04506.64|
nspsend:38 29 0D 0A 48 6F 73 74 3A 20 31 39 32 2E 31 36 38 2E 31 2E 31
30 33 3A 38 30 33 33 0D 0A 50 72  |8)..Host: 192.168.1.103:8033..Pr|
nspsend:6F 78 79 2D 43 6F 6E 6E 65 63 74 69 6F 6E 3A 20 4B 65 65 70 2D
41 6C 69 76 65 0D 0A 0D 0A 00 00  |oxy-Connection: Keep-Alive......|

Does someone has a clue to make it work?

Damien B

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
--
OpenSTA-users mailing list OpenSTA-users@...
Subscribe/Unsubscribe/Options: http://lists.sf.net/lists/listinfo/opensta-users
Posting Guidelines: http://portal.opensta.org/faq.php?topic=UserMailingList

[Dan Downing]

Damien wrote:

>Sent: Thursday, January 24, 2008 4:58 PM
>To: opensta-users@...
>Subject: [OpenSTA-users] Gateway.exe infinite loop
>Hello,
>I write here before opening a bug in order to get some input.
>Here is the configuration:
>- OpenSTA 1.4.4.11
>- Windows XP SP2
>- Browser IE7 and Firefox (same behaviour)
>
>While recording a script:
>- gateway listening on 192.168.1.103:81
>- target server is 192.168.1.103:8033 (same machine)
>- fetching the very first URL (IE or Firefox address bar + <enter>),
>gateway.exe goes 100% on the CPU, and opens a load connexions.

Damien:  try using IE6 instad of IE7 or Firefox, as Opensta does not support
either of those browsers.

...Dan
www.mentora.com




-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
--
OpenSTA-users mailing list OpenSTA-users@...
Subscribe/Unsubscribe/Options: http://lists.sf.net/lists/listinfo/opensta-users
Posting Guidelines: http://portal.opensta.org/faq.php?topic=UserMailingList

[Daniel Sutcliffe-4]

Damien B wrote:
> I write here before opening a bug in order to get some input.

Thank you for doing this - you have not found a bug and this is
exactly why I ask people to post here before logging one.

> Here is the configuration:
> - OpenSTA 1.4.4.11
> - Windows XP SP2
> - Browser IE7 and Firefox (same behaviour)

Both IE7 and the latest Firefoxes are known to have issues with the
OpenSTA gateway recording mechanism, specifically for HTTPS sites,
but they can be made to work with regular sites if you know what you
are doing.

> While recording a script:
> - gateway listening on 192.168.1.103:81
> - target server is 192.168.1.103:8033 (same machine)
> - fetching the very first URL (IE or Firefox address bar + <enter>),
> gateway.exe goes 100% on the CPU, and opens a load connexions.
>
> Here is the begininning of the console:
> Running in default mode (as a console)...
>
> Initialize the gateway...
> Listening on < 192.168.1.103:3000>.
> Gateway is running...
> Connection from <192.168.1.103:2759>.
> Listening default on <192.168.1.103:81 > for <> using gwhttp.dll.
>
> Original Browser configuration
> ------------------------------
> Proxy Configuration : HTTP:POROP103:81;SSL:POROP103:81;FTP:POROP103:81;GOPHER:PO
> ROP103:81;SOCKS:POROP103:81
> Exceptions :
> Local Proxy Value : proxy_for_local

We see here that the proxy in you browser is already set to be port
81 of your local machine before the Gateway starts up and modifies
it to be this.  The effect of this is to create a proxy loop - the
Gateway uses the existing proxy to be the proxy it will pass the
traffic on to.  So effectively it passes the same traffic on to
itself.

Unless you have a real proxy you want to pass onto you should not
have a proxy set up in your browser if you are using the automatic
recording mechanism (where the Modeler starts the browser).

I would also suggest not trying to record and test any Web site
running on the same machine as OpenSTA unless you absolutely cannot
avoid it - there are just too many things that can go wrong and casue
confusion, so you are asking for trouble.

Cheers
/dan
--
Daniel Sutcliffe <DanSut@...>
  OpenSTA part-time caretaker - http://OpenSTA.org/

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
--
OpenSTA-users mailing list OpenSTA-users@...
Subscribe/Unsubscribe/Options: http://lists.sf.net/lists/listinfo/opensta-users
Posting Guidelines: http://portal.opensta.org/faq.php?topic=UserMailingList