lynx-dev lynx proxy IP lookups (fwd)

[groggy]

please bare with me, if possible.
i have spent 6 hours verifying this problem,
and have tried to be as brief and straighforward
as i can be.

nslookup, telnet, ftp, traceroute, ping, etc
all work fine and dandy on both client
and server (goto end for problem),
in both numerical, symbolic, aliased,
and REAL IP formats ...

----------
CLIENT   
----------
/etc/hosts

127.0.0.1    localhost lh
192.168.0.13 aliasingateway

/etc/resolv.conf

# my clients bogus domain (i need to connect to various
# ppp aliasing gateways, so hopefully this is OK ...
domain         abc.xyz.net
nameserver     127.0.0.1

/etc/host.conf

hosts
bind
# nis

/etc/named.boot

;type          ;domain                       ;source host/file
directory      /etc/namedb
forwarders     192.168.0.13                  ;aliasingateway
cache          .                             cache.db
primary        0.0.127.in-addr.arpa          localhost.rev
primary        abc.xyz.net                   abc.xyz.net.db

----------
SERVER   
----------
/etc/hosts

127.0.0.1    localhost lh
192.168.0.13 aliasingateway

/etc/resolv.conf

domain         aliasingateway.net
nameserver     127.0.0.1

/etc/host.conf

hosts
bind
# nis

/etc/named.boot

;type          ;domain                       ;source host/file
directory      /etc/namedb
forwarders     234.235.236.237               ;isp ns
cache          .                             cache.db
primary        0.0.127.in-addr.arpa          localhost.rev
primary        abc.xyz.net                   abc.xyz.net.db
primary        0.168.192.in-addr.arpa        aliasingateway.rev

-------------------------------------
PROBLEM:

i need lynx to use my clients httpd server
when i'm not connected to my "aliasingateway".

i need lynx to be able to use my aliasingateway's
httpd server to serve it's web pages also, when
i'm connected to it.  it uses squid ...

i have lynx using the :

http_proxy:http://192.168.0.13:3128/
------------------------------------
directive. with :

#no_proxy

all lynx "localhost" requests on the client
get web pages off the aliasingateway, as
might be expected.  all lynx "192.168.0.13"
(aliasingateway) requests end in squid
"connection failed, no route to host"
errors.  all lynx "123.123.123.123"
(aliasingateway REAL IP) requests
seem to work as expected, fetching
pages from the aliasingateway's
filesystem.  this is no good
because the localhost requests
don't get the HTML pages off
the clients filesystem.
----------------------------
with :

no_proxy:localhost,127.0.0.1

all lynx "locahost" requests on the client
get web pages off the clients httpd server, as
would be expected.  but all "192.168.0.13"
requests fail with a squid error "connection
failed, no route to host" ...  i don't
know if this is normal or not.  all
"123.123.123.123" (aliasingateway's
REAL IP) requests get pages off
the aliasingateway, BUT only
*** if they are FULLY specified! ***

BUG ???

ie, if i want an "index.html" pages from
a directory, but only specify "123.123.123.123/dir",
the page comes from my CLIENTS filesystem!

ie, but if i specify "123.123.123.123/dir/index.html",
the pages comes off the ALIASINGATEWAY's filesystem!
this is what made it hard for me to initially debug
this problem since my filesystems were basically
mirrors of each other.
--------------------------------------------------------
with :

no_proxy:localhost,127.0.0.1,aliasingateway,192.168.0.13

all lynx "locahost" requests on the client
get web pages off the clients httpd server, as
would be expected.  all "192.168.0.13" (aliasingateway)
and all "123.123.123.123" (aliasingateway's REAL IP)
requests get pages off the aliasingateway, BUT only
*** if they are FULLY specified! ***

BUG ???

ie, if i want an "index.html" pages from
a directory, but only specify "123.123.123.123/dir",
the page comes from my CLIENTS filesystem!

ie, if i specify "192.168.0.13/dir/index.html",
or  if i specify "123.123.123.123/dir/index.html",
the pages comes off the ALIASINGATEWAY's filesystem!
-----------------------------------------------------------
with :

no_proxy:localhost,127.0.0.1,aliasingateway,123.123.123.123

the results are the same as above ...
-----------------------------------------------------------

i hope this isn't too confusing.