InetGetSource Vs InetGet

[Unc3nZureD]

Try the following source:

$a = _INetGetSource("http://encryptedchat.fulba.com/uncenzured.txt")

InetGet("http://encryptedchat.fulba.com/uncenzured.txt", @ScriptDir & "asd.txt", 1, 0)

MsgBox(0, "", FileRead(@ScriptDir & "asd.txt"))

MsgBox(0, "", $a)

Exit

Meanwhile _InetGetSource returns non UTF-8 string, Inetget will get the correct file. Why and how to solve? I tried to retrieve it as binary, but it's all the same. Am I forced to use InetGet?

Edited January 30, 2014 by Unc3nZureD

[mikell]

$oHTTP = ObjCreate("Microsoft.XMLHTTP")
$oHTTP.Open("GET", "http://encryptedchat.fulba.com/uncenzured.txt", 0)
$oHTTP.Send()
Local $txt = $oHTTP.Responsetext 
$oHTTP = 0
MsgBox(0, "", $txt)

?

[Unc3nZureD]

Well, that's a nice solution, I'll use that Anyways, any idea why the _InetGetSource Isn't working properly?

[mikell]

InetGet gets the same data than _InetGetSource, but FileRead can detect the encoding and returns the correct string

[Unc3nZureD]

Then I think they should improve the InetRead, to detect the encoding

[mikell]

Ahem, sorry... I forgot that

$a = InetRead("http://encryptedchat.fulba.com/uncenzured.txt")
MsgBox(0, "", BinaryToString($a, 4))

[Unc3nZureD]

Oh, does it have such arguement? Good to know Thanks.