Reed Martin wrote:
> 
> Okay,
> 
> Remember our pal LibURL, and how Andu told us all how to comment out the
> line that was unnecessary since it would leave sockets open? Well I'm now
> using the modified LibURL that came with 2.4B3, and having a problem...
> 
> Using the "post" command, it seems to cut off a good fraction of the end of
> the file, while not closing the socket. Let's say the contents of myURL
> (http://www.myurl.com/mycgi.cgi) is supposed to be "a\b\c\d\e\f\g\h\i"
> (where "\" is a return)... When I do:
> 
> post myStuff to url myUrl
> put it into urlReply
> 
> urlReply isn't complete (eg, it looks like: "a\b\c\d\e\f\g") and
> 
> answer openSockets()
> 
> reveals that the socket is still open.
> 
> Trying the above script with post a second time does nothing. So I close
> the open socket, and then try the above script using post again. This time,
> the last part of urlReply that was missing is at the beginning, followed by
> the actual urlReply data, but missing the last part again. (eg, it looks
> like: "h\i\a\b\c\d\e\f\g")
> 
> This time, interestingly, there is no remaining open socket. However, doing
> the post script a third time results in the above, plus the same again.
> (urlReply gets progressively longer with each subsequent "post" attempt...
> eg, it looks like: "\h\i\a\b\c\d\e\f\g\h\i\a\b\c\d\e\f\g")
> 
> Any ideas? I looked through the libURL stack script but I can't locate
> where the problem is. I'm guessing it's in the "readmore" script, but I'm
> just not sure.
> 
> Thanks for your help!
> 
> Reed
> 
> Archives: http://www.mail-archive.com/[email protected]/
> Info: http://www.xworlds.com/metacard/mailinglist.htm
> Please send bug reports to <[EMAIL PROTECTED]>, not this list.

The never ending story... Send me the url so that I can see what
happens.

-- 
Regards, Andu
_______________
[EMAIL PROTECTED]

Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.

Reply via email to