On Apr 01, 2006 10:45 AM, jis wrote: > 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
What are you referring to when you say: "webservers use ErrorCode 103 as "Access not allowed" when the needed SetRequestHeaders are wrong" To the error code that the Socket issues or to the HTTP Status code the webserver sends in its response? If to the Socket error, then, in my opinion, is wrong because error 103 is only issued when RB is unable to resolve the address that was specified. If to the webserver HTTP Status response, then that's new to me, because the error 103 does not even exist on the RFC 2616: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html 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>
