Sahi and gwt-comet = comet connection aborted

noosy

Hi,

I would really like to use Sahi to do some web app testing for my gwt application which uses the gwt-comet library (a Comet implementation for Google Web Toolkit).

Since I am new to this forum it appears I can't post images so please bare with me while I try to describe what I am seeing in firebug.

When the browser is NOT pointing to the Sahi Proxy, and users login to my app, the following GET request is made to establish a comet connection. The GET request remains in [Receiving] mode while the comet connection is still there:

GET myComet? 200 OK myhost:myport ?(x.xKB) [Recieving]

What I have just described is normal working behaviour for my app.

When the browser IS pointing to the Sahi Proxy, and users login to my app, the GET request is almost immediately aborted:

GET myComet? Aborted myhost:myport ? [NaNm NaNs Recieving]

As a result, my user is disconnected (logged out) from my app almost immediately.

I am using Firefox 3.6.13/Windows XP

Firefox Connection Settings:

Manual proxy configuration:
HTTP Proxy: hostRunningSahi
Port: 9999
No Proxy for: blank

Sahi build: Sahi V3 Release 2010-11-03

I have tried to get to the bottom of this using Wireshark but it is not revealing much to me. I can see that the GET request is passing through the Sahi proxy OK and in a timely manner but otherwise I do not see what the problem is.

I have configured sahi.properties as follows (default values with the expection of the following):

# Set this to 2 if browser seems to be idle for a long time during to AJAX calls.
# Use 1,2,3 for ZK apps. Just 2 for gmail (and comet based applications).
# Can be controlled in the script using _sahi.waitWhenReadyState1, _sahi.waitWhenReadyState2, _sahi.waitWhenReadyState3
xhr.wait_ready_states=2

I would really appreciate some guidance on how I can overcome this problem. My understanding is that Sahi can handle Comet connections so this behaviour is unexpected. The gwt-comet library has been tested with an Apache proxy without any issues so my expectation is that the Sahi proxy should not be a show stopper for the gwt-comet library.

Many thanks.

narayan

Hi Noosy,

We are looking into this. Will get back to you.

Regards,
Narayan

noosy

Hi Narayan,

How are things progressing?

Thanks,

Vanessa

narayan

Vanessa,

Is this happening with all browsers? Could you check if the browser is using HTTP 1.1 (Persistent connections) when using a proxy?

If you are checking with wireshark, could you see whether its is reporting HTTP 1.0 or HTTP 1.1?

Regards,
Narayan

noosy

Hi Narayan,

I have only tested under Firefox and Chrome and I experience the same problem in both browsers.

HTTP 1.1 is being reported.

Let me know if I can provide any further details.

Cheers,

Vanessa