Wierd URL problems


#1

I began noticing on my dev machine that URL::readEntireTextStream was taking forever to return (on Windows)… to the point that often it would just hang and timeout. Around the same time I started getting reports from beta testers of the same problem. Out of curiosity, I tried to view the text file in IE, and IE exhibits the same behavior (but for every URL I try). As if there’s some nasty DNS cache problem going on. The file downloads fine in Firefox, or anything else FTM. No idea if they’re at all related, just wondering if anyone else is experiencing this before I go digging through the wininet stuff.

Thx :slight_smile:


#2

my advice is don’t use it, use curl if you can, there are too many places it can fail with wininet internals, maybe your using some sort of proxy?