Sorry, my mistake. For some reason I confused #103 with #304.
Here a small example:
dim temp as string, http as HTTPSocket
http = new HTTPSocket
temp = HTTP.Get("http://teletekst.nos.nl/tekst/520-01.html";, 5)
http.Close
msgBox temp
break
http = New HTTPSocket
http.SetRequestHeader ("Host", "teletekst.nos.nl")
http.SetRequestHeader ("Connection", "keep-alive")
http.SetRequestHeader ("User-Agent", "Mozilla/5.0 (Macintosh; U;
PPC Mac OS X; en) AppleWebKit/125.5.7 (KHTML, like Gecko) Safari/
125.12")
http.SetRequestHeader ("Accept", "*/*")
http.SetRequestHeader ("Accept-Encoding", "gzip, deflate;q=1.0,
identity;q=0.5, *;q=0")
http.SetRequestHeader ("Accept-Language", "en, ja;q=0.50")
temp = http.Get("http://teletekst.nos.nl/tekst/520-01.html",5)
msgBox temp
On 01/04/2006, at 12:55 PM, Carlos M wrote:
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>
