🚀 go-pugleaf

> You can't do that.  The Browser can only be accessed in the context of the
> thread that created it.  You cannot access it across thread boundaries
> (without manually marshalling the ActiveX interface, which can get ugly).
>
That I didn't know. I can see about creating the browser in the context of 
the
thread then, but as I recall I had problems with it not staying hidden. It 
was
months ago that I wrote this so I'll have another go at it.

>> IE6 and below function just fine.
>
> I seriously doubt that.
It wasn't throwing errors with IE6, which tells me they didn't have it setup
in the same fashion. Maybe it should have been, but it did work (and still)
does for my clients. In either case as I stated above I'll try creating it 
inside
the thread.

> The UserAgent is the only application-specified identifer available.  If 
> you
> set Indy's UserAgent to match IE's, there is no other way a website can
> differentiate between the two.

There's absolutely nothing else with how it sends it's requests correct?
If I check the rawheaders when the request is sent the UA shows up just
fine, but the URL I provided in my original post fails. That same URL in
a browser succeeds. If necessary I'll post a small program with sources
showing exactly what I'm doing to reproduce it for you...

-Tom