Ian Clarke <ian at freenetproject.org> writes: > 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... [...] > I guess we could also determine in real-time whether the URL looks like an > FProxy link, or whether it looks like a NodeInfoServlet link.
Would it be too restricting to specify freenet keys to either start with an upcase letter (C, S, or K at the moment), or with "freenet:"? Anything else is a special command, for example a nodeinfo servlet, something that modifies fproxy behaviour, or whatever. This may allow us to migrate away from the ugly <a href="__CHECKED_HTTP..."> to e.g <a href="/http/freenetproject.org/cgi-bin/twiki/view/Main/WhatIs">. On the downside, we'd have to implement more filtering to avoid links to the "/shutdown" servlet. -- Robbe -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.ng Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20020907/97d60979/attachment.pgp>
