Gianni Johansson <giannijohansson at attbi.com> writes: > / -- with no arguments would map to Ian's infolet main page > -- with a valid URI, maps to a leaner and meaner fproxy-lite servlet that > handles normal requests and inserts but redirects splitfile > inserts /requests to he servlets below. > /servlet/splitfile_insert -- inserts a FEC encoded splitfile > /servlet/splitfile_retrieve -- retrieves a fec encoded splitfile > /servlet/cool_thing_no_one_has_thought_of yet -- it's easy to add new stuff
Sounds good. Except I'd like to have the URLs as short as possible, before they're set in stone. Nobody cares that this is a servlet internally, so let's just use /x/ or /_/ or /./ as the special prefix. Or (I already suggested that) drop the prefix and restrict servlets to have names easily distinguishable from freenet keys (we will lose the ability to make /gpl.txt mean /KSK at gpl.txt, but KSKs aren't as hip as they were in our youth, anyway). We will also have to think about access from freesite pages. Will links to /_/some_service be allowed? Redirects? Triggered javascript? This may make sense for some servlets and not for others. We could put the safe class under /s/ and unsafe ones under /u/. There could be a generalised version of the __CHECKED_HTTP_ handler named /s/u/, so that surfing to /s/u/dangerous will bring up a confirmation page, that links you to the real /u/dangerous. __CHECKED_HTTP__freenetproject.org will get /s/u/http/freenetproject.org The safeness of a servlet need not be encoded in its name (and if it isn't it is easier to reconfigure locally). Every servlet could register whether it is safe (overridable from the config file). fproxy will not barf on links to unsafe servlets, but rewrite them to checked links on the fly. -- 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/20020912/3e6a72f3/attachment.pgp>
