Half true (;o)
Many webservers use ErrorCode 103 as "Access not allowed" when the
needed SetRequestHeaders are wrong or lacking. This is not contrary
to what the LR states about #103 and different from #501, which
forbids browsers to access a particular url.
Johan Simons
On 01/04/2006, at 9:25 AM, Carlos M wrote:
On Mar 31, 2006 4:45 PM, Phil M wrote:
On Mar 30, 2006, at 11:53 PM, jis wrote:
Error 103 means "Rejected by server"
This explanation is quite unlikely (though possible) for a web
server. Usually for HTTPSockets Error Code #103 means that the
server cannot be found (like a bad URL).
Exactly... or something is preventing the HTTPSocket to reach the
destination server, like a Firewall.
LR says about error 103: "Name Resolution Error - REALbasic was unable
to resolve the address that was specified. A prime example of this
would be a mistyped IP address, or a domain name of an unknown or
unreachable host."
Normally a webserver would use one of the HTTPStatus
codes (such as #501) to notify the user that the
requested URL is forbidden.
HTTP Status code for Forbiden is #403. #501 means "Not Implemented -
The request was unsuccessful because the server can not support the
functionality needed to fulfill the request."
Carlos
_______________________________________________
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>
