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 the = > nice=20 > menu to the left, and can't really support controlling of the entire=20 > web-browser window, which is why we need FProxy. > > Now, we could - say - set it up so that going to : > > http://localhost:8890/fproxy/CHK%40... > > Works like going to: > > http://localhost:8888/CHK%40... > > does now - however we would no-longer be able to take advantage of links to= > the=20 > server root (ie. hyperlinks which begin with "/"). That would be unfortuna= > te. > > I guess we could also determine in real-time whether the URL looks like an= > =20 > FProxy link, or whether it looks like a NodeInfoServlet link.
???(@|%40).* is a damm good guess it's a FProxy link. Basically, if it's not an infolet, it's a key. If the keyparse fails, it's a 404. --Dan _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
