On Thu, 2002-10-10 at 03:22, Edgar Friendly wrote: > David Allen <[EMAIL PROTECTED]> writes: > > > Is there something terribly obvious I'm missing or is this a bug? > > > > Running build 513, updated today, I tried something to see what would > > happen. > > > > Fetch this key: > > SSK@rBjVda8pC-Kq04jUurIAb8IzAGcPAgM/FF//cant/possibly/exist/dammit > > > > Why does this pull up the front page of Freenet Forever? > > > The metadata spec doesn't specify behavior for a name that's not > listed in the control document. [snip] > > If it's what most clients do, then it's standard. There's no real > need to give an error result when requesting an unknown name, and the > easiest thing to do is use the default field to determine the action. > > If you want to make a case why I should put my foot down and spec it > one way or the other, go ahead. The only sorta-special case that's > needed is for the default name to match "". > It seems to me that this behaviour is inconsistent with what people are used to with their web browser, and therefore confusing.
If I'm wandering around a freesite, and click on a link that is for some reason broken, I don't expect to suddenly find myself back on the site's home page. Personally, I'd rather see something equivalent to the familiar "404 Document not found" message. Or else the browser should just stay where it is. I thinks it's more a question of encouraging FProxy (and other clients) to behave nicely, rather than changing the metadata spec. cheers Chris -- Chris Dennis Bristol, UK _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
