Sign in to follow this  
Followers 0
Unc3nZureD

InetGetSource Vs InetGet

7 posts in this topic

#1 ·  Posted (edited)

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 by Unc3nZureD

Share this post


Link to post
Share on other sites



$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)

?

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0