[REBOL] Re: Proxy Problems (Was: Re: Fixes View: 0.10.29 Re:(2))
From: ssayer::acuson::com at: 5-Sep-2000 12:31
I think the error you report is secondary to the atypical proxy
configuration architecture REBOL has adopted.
You'll notice that the error you received indicates it's using the tcp
scheme. It used to be that the REBOL sites for view were accessed with
http, and while the http scheme relies to some degree on the tcp scheme to
do it's thing, I think you'll find like me that the following will work
The problem I believe comes down to REBOL's association of proxy use with
scheme rather than port and transport protocol (tcp, udp), the more
typical manner in which firewalls restrict access to network resources.
The deviation from this proxy configuration architecture by the nature of
their using tcp rather than http to read resources for the View interface
gives a glimpse of other proxy related issues that will inevitably arise
secondary to this approach.
I'm sure many of us can appreciate the implications of this, i.e. we now
have to configure REBOL to also direct tcp scheme connections through the
proxy to handle "built-in" View connections but tcp scheme connections to
server ports not used for http will no longer work because the proxy won't
handle them. Soon we'll find ourselves rewriting the proxy settings in the
system in our code to accomodate connections based on connection port.
This I'm sure is not what was intended by the design.
In my report to feedback on this and the other side effects of this you
haven't mentioned, I hope to suggest that they revisit the approach to
This is clearly a challenging issue for such a highly versatile product
and I'm sure our friends at REBOL Technologies will strive to provide a
solution that is loyal not only to it's commitment to be portable across
platforms but also to network security architectures.
On Mon, 4 Sep 2000