[freenet-dev] Fproxy changes

2002-09-08 Thread Dan Merillat
Matthew Toseland writes: > Just allow access to : AND :8890. The code does not make it > absolute, it takes the hostname from the query. Let's see. I access via http://free/ It redirects me to http://:8890/ --Dan ___ devl mailing list devl at

Re: [freenet-dev] Fproxy changes

2002-09-07 Thread Dan Merillat
Matthew Toseland writes: > Just allow access to : AND :8890. The code does not make it > absolute, it takes the hostname from the query. Let's see. I access via http://free/ It redirects me to http://:8890/ --Dan ___ devl mailing list [EMAIL

[freenet-dev] Fproxy changes

2002-09-07 Thread Robert Bihlmeyer
Ian Clarke writes: > Now, we could - say - set it up so that going to : > > http://localhost:8890/fproxy/CHK%40... > > Works like going to: > > http://localhost:/CHK%40... [...] > I guess we could also determine in real-time whether the URL looks like an > FProxy link, or whether it looks

Re: [freenet-dev] Fproxy changes

2002-09-07 Thread Robert Bihlmeyer
Ian Clarke <[EMAIL PROTECTED]> writes: > Now, we could - say - set it up so that going to : > > http://localhost:8890/fproxy/CHK%40... > > Works like going to: > > http://localhost:/CHK%40... [...] > I guess we could also determine in real-time whether the URL looks like an > FProxy link,

[freenet-dev] Fproxy changes

2002-09-06 Thread Matthew Toseland
On Wed, Sep 04, 2002 at 11:27:22PM -0400, Dan Merillat wrote: > > Ok, let it be said I love the new UI. However, since : is just > redirecting > to :8890, can't we just merge the two interfaces? > > It screws up my setup of using squid to redirect freenet requests, but I > think I > can wo

Re: [freenet-dev] Fproxy changes

2002-09-06 Thread Matthew Toseland
On Wed, Sep 04, 2002 at 11:27:22PM -0400, Dan Merillat wrote: > > Ok, let it be said I love the new UI. However, since : is just redirecting > to :8890, can't we just merge the two interfaces? > > It screws up my setup of using squid to redirect freenet requests, but I think I > can work ar

[freenet-dev] Fproxy changes

2002-09-05 Thread Dan Merillat
Ian Clarke writes: > > --S1BNGpv0yoYahz37 > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > Well, in theory - yes, in practice, it ain't so easy. > > The NodeInfoServlet resides on port 8890, that is the thing that draws

Re: [freenet-dev] Fproxy changes

2002-09-05 Thread Dan Merillat
Ian Clarke writes: > > --S1BNGpv0yoYahz37 > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > Well, in theory - yes, in practice, it ain't so easy. > > The NodeInfoServlet resides on port 8890, that is the thing that draw

[freenet-dev] Fproxy changes

2002-09-04 Thread Dan Merillat
Ok, let it be said I love the new UI. However, since : is just redirecting to :8890, can't we just merge the two interfaces? It screws up my setup of using squid to redirect freenet requests, but I think I can work around it. Perhaps. It's a pain to rewrite URLs on the fly, so I may have

[freenet-dev] Fproxy changes

2002-09-04 Thread Ian Clarke
Well, in theory - yes, in practice, it ain't so easy. The NodeInfoServlet resides on port 8890, that is the thing that draws the nice menu to the left, and can't really support controlling of the entire web-browser window, which is why we need FProxy. Now, we could - say - set it up so that goi

Re: [freenet-dev] Fproxy changes

2002-09-04 Thread Ian Clarke
Well, in theory - yes, in practice, it ain't so easy. The NodeInfoServlet resides on port 8890, that is the thing that draws the nice menu to the left, and can't really support controlling of the entire web-browser window, which is why we need FProxy. Now, we could - say - set it up so that go

[freenet-dev] Fproxy changes

2002-09-04 Thread Dan Merillat
Ok, let it be said I love the new UI. However, since : is just redirecting to :8890, can't we just merge the two interfaces? It screws up my setup of using squid to redirect freenet requests, but I think I can work around it. Perhaps. It's a pain to rewrite URLs on the fly, so I may have