A few month ago I made this question and the answer was:
103 means connection rejected by server
In these cases you should include:
httpSocket1.SetRequestHeader ("Host", "url without http://.com";)
httpSocket1.SetRequestHeader ("Connection", "keep-alive")
httpSocket1.SetRequestHeader ("User-Agent", "Mozilla/5.0 (Macintosh; U; PPC
Mac OS X; en) AppleWebKit/125.5.7 (KHTML, like Gecko) Safari/ 125.12")
httpSocket1.SetRequestHeader ("Accept", "*/*")
httpSocket1.SetRequestHeader ("Accept-Encoding", "gzip,
deflate;q=1.0, identity;q=0.5, *;q=0")
httpSocket1.SetRequestHeader ("Accept-Language", "en, ja;q=0.50")
HTH,
Alexander
At 11:45 a.m. 31/03/2006, you 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). Normally a webserver would
use one of the HTTPStatus codes (such as #501) to notify the user
that the requested URL is forbidden.
_______________________________________________
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>
_______________________________________________
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>
|