chesterpolo / mongoose

Automatically exported from code.google.com/p/mongoose
MIT License
0 stars 0 forks source link

Always persistent connection #61

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Found another problem with IE any version....
The persistent connection detaches itself but it dies... immediatly.

The question was resolved in the "persistent thread" but this does work
only with Firefox. All versions of IE seems not to work....
Sorry

Original issue reported on code.google.com by diao...@gmail.com on 24 Jun 2009 at 10:25

GoogleCodeExporter commented 9 years ago
Please elaborate more on that, I did not get the problem.

Original comment by valenok on 28 Jun 2009 at 8:52

GoogleCodeExporter commented 9 years ago
I don't understand the problem either.

Original comment by googl...@springtimesoftware.com on 28 Jun 2009 at 4:36

GoogleCodeExporter commented 9 years ago
If you probe this simple cgi you can see that on Mozilla you get the time that 
changes every 5 seconds....
On IE, all versionsit doesn't work at all.

The attached cgi is a simple test that reproduces a connection from mongoose to 
the 
browser... 
Tx....

Original comment by diao...@gmail.com on 29 Jun 2009 at 6:10

Attachments:

GoogleCodeExporter commented 9 years ago
I need a persistent connection from the server itself for verifying that the 
window
is open.
Working with MozillaFirefox when you close the requested window the server 
receives a
SIOGADDRFAILED and despite it closes the attached cgi with a SIGQUIT alarm.

THe same does not work when using IE(all versions).

Is it a script problem? With apache it does work with all browsers.

Tx, Diaolin

Original comment by diao...@gmail.com on 29 Jun 2009 at 10:15

GoogleCodeExporter commented 9 years ago
Did you find any solution????

If you probe this simple cgi you can see that on Mozilla you get the time that 
changes every 5 seconds....

instead if you try this on Internet Explorer it does not work... 
the persistent connection detaches itself and dies immediatly...

Tx

Original comment by diao...@gmail.com on 26 May 2010 at 6:07

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by valenok on 7 Sep 2010 at 8:41

GoogleCodeExporter commented 9 years ago
I still don't understand. But a CGI that should be run once should not be run 
repeatedly. If that's what's happening, it is a bug that should be fixed. Just 
saying.

Original comment by googl...@springtimesoftware.com on 7 Sep 2010 at 8:49

GoogleCodeExporter commented 9 years ago
Sorry but this cgi, those included in the third comment, sloud run until the 
explorer window will be closed. WIth firefox it works right, with explorer 
no....

Original comment by diao...@gmail.com on 7 Sep 2010 at 9:38

GoogleCodeExporter commented 9 years ago
I don't think your CGI script sends correct chunked data.

Original comment by valenok on 7 Sep 2010 at 10:03

GoogleCodeExporter commented 9 years ago
Ok, but did you test it?????
Or is only a suspect?

Original comment by diao...@gmail.com on 8 Sep 2010 at 6:30

GoogleCodeExporter commented 9 years ago
In any case... why firefox and ie6 are ok and IE7-8 are not??? 

Original comment by diao...@gmail.com on 8 Sep 2010 at 6:31

GoogleCodeExporter commented 9 years ago
Yes I ran it, and also looked at the code.
It does not produce valid chunked-encoded output.

Original comment by valenok on 9 Sep 2010 at 12:37

GoogleCodeExporter commented 9 years ago
No???
any hint?

Original comment by diao...@gmail.com on 9 Sep 2010 at 12:55

GoogleCodeExporter commented 9 years ago
be aware of cross platform problem for new line issue in different platforms.

:
LINE 10: my $CRLF = "\015\012";   # "\r\n" is not portable
:

source: 
http://cpansearch.perl.org/src/GAAS/libwww-perl-5.836/lib/HTTP/Message.pm

Original comment by akarc...@gmail.com on 10 Sep 2010 at 12:48

GoogleCodeExporter commented 9 years ago
But, where did you find this problem in the test_persistent???

you mean the "\n\n" in the code???

But, vale...@gmail.com says tht the Chunked-encoding is not good...

i don't know why...

Tx, Diaolin

Original comment by diao...@gmail.com on 10 Sep 2010 at 6:12

GoogleCodeExporter commented 9 years ago
The problem here seems to be that people are saying things like "it doesn't 
work" without explaining clearly exactly what isn't working and presenting 
their evidence. Without such full information is it impossible for Sergey to 
understand you fully, much less fix the problem.

Maybe you folks need to get on a text chat together, instead of continuing to 
use Google Code. Get your communication done, then return here to track the bug 
fix.

I hope that observation helps.

And, Sergey, you might want to change the Status to an Open status like New 
until the issue is clear.

Original comment by googl...@springtimesoftware.com on 10 Sep 2010 at 11:51

GoogleCodeExporter commented 9 years ago
Nono, sorry i've explained, but probably it wasn't sufficient

Sorry.

Original comment by diao...@gmail.com on 10 Sep 2010 at 3:48

GoogleCodeExporter commented 9 years ago
Not necessary to be sorry. Get a chat connection with Sergey and stop posting 
here. Thanks.

Original comment by googl...@springtimesoftware.com on 10 Sep 2010 at 4:35

GoogleCodeExporter commented 9 years ago
Why?
Is this the wrong place for mongoose???

Original comment by diao...@gmail.com on 12 Sep 2010 at 5:36