Yes, I'll give the socketTimeOutInterval a try. As for the headers returned by libUrlSetLogField, they look pretty much like the example you show here, except that on one or two occasions a content length line of 83 or 84 was included.
Greg
On Saturday, February 1, 2003, at 01:07 AM, [EMAIL PROTECTED] wrote:
Message: 2 Date: Fri, 31 Jan 2003 17:11:51 +0000 To: [EMAIL PROTECTED] From: Dave Cragg <[EMAIL PROTECTED]> Subject: Re: POST Command Reply-To: [EMAIL PROTECTED]At 11:42 am -0500 31/1/03, Gregory Lypny wrote:Hi Dave, Thanks for responding. Yes, I have checked the result function after the post, and it is always empty. If I omit the CDML tag -Max=All from my post, I immediately get the default 25 records returned. And curiously, when I transfer the database to my local Mac and post to localhost, as I mentioned, all records are, in fact, returned.To check if it's just a timeout, try increasing the socketTimeoutInterval. The default is 10000 (milliseconds). Try setting it to 30000. What is logged when you use libUrlSetLogField? It should show the http headers returned by the server. I've only used Filemaker's xml features (different from CDML I think), but I guess the format should be similar. Here, the headers look something like this: HTTP/1.1 200 OK Date: Fri, 31 Jan 2003 16:19:28 GMT Server: FileMakerPro/5.5v2 WebCompanion/5.5v3 MIME-Version: 1.0 Transfer-Encoding: chunked Content-Type: text/xml; charset=utf-8 Expires: Tue, 12 Nov 1963 00:36:00 GMT Anything significantly different in your case? In particular, is there a Content-Length or Transfer-Encoding field? Cheers Dave
_______________________________________________ metacard mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/metacard
