On Tue, 14 Sep 1999, Kevin Miller wrote:
> On Tuesday, Sept 14 1999, Scott Raney wrote:
>
> >> Are you sure you got the address of the proxy server correct, complete with
> >> port? Is it the same as the settings used in Netscape, for example?
> >
> > Also note that only one type of HTTP proxy is currently supported, the
> > one where you have a specific host name or IP address. The other kind
> > has you access a file on your side of the firewall that contains the
> > address of the proxy. If that's the kind your browser is set up to
> > use, you can usually get the address of the other kind by asking your
> > system administrator.
>
> System administrators often supply these nowadays to make it easier to
> configure a client. (Having recently upgraded our LAN I've spent a while
> fighting this stuff.) However, that address only refers to a configuration
> file that contains all the other addresses, so you should be able to
> open/download that and look, or guess the proxy from the address for that
> file (it will typically be the same IP with whatever port you use for HTTP,
> usually 80 or 8080). Any plans to support this kind of auto-configuration
> in MetaCard?
Even if we solve this problem, you're still left with the one of
figuring out what to set the httpProxy property to, which in some
cases is a rather difficult problem to solve. Current thinking is to
move HTTP support out of the engine entirely and make it a standard
scripted solution using the new socket features. This will make it
much easier to add new features like these, and allow people with
special needs to build custom solutions.
Regards,
Scott
********************************************************
Scott Raney [EMAIL PROTECTED] http://www.metacard.com
MetaCard: You know, there's an easier way to do that...
