realbasic-nug
[Top] [All Lists]

Re: Synchronous HTTP requests

To: REALbasic NUG <realbasic-nug at lists dot realsoftware dot com>
Subject: Re: Synchronous HTTP requests
From: Phil Mobley <phil at mobleybros dot com>
Date: Thu, 30 Dec 2004 15:30:13 -0800
Delivered-to: realbasic-nug at lists dot realsoftware dot com
References: <3C70D4ED-5ABA-11D9-951A-000A95A9544A at shaw dot ca>
On Dec 30, 2004, at 3:26 PM, Norman Palardy wrote:

Just wondering about using these as they make sense for some things I am trying to do However, the error codes don't seem to function the way I might expect.

Say I make a request for a file that does not exist and the server returns an error (say a 404 Not found)

With the synchronous version I'm not seeing the error reported as a 404 I get errorCode set = 0 and last error code = 102. But I get that same errorCode and lastErrorCode when the request is successful

That doesn't make sense to me or do I have to check the actual content returned to see what happened

I think those errors are just for connection errors, though it would be really nice if the HTTPSocket could work that way.

I think that you need to parse the HTTP Status code from the headers.

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>

<Prev in Thread] Current Thread [Next in Thread>