> From: Matthew Toseland <toad at amphibian.dyndns.org> > Date: 23 Oct 2002 10:51:27 +0100 > > On Wed, Oct 23, 2002 at 01:22:54AM -0400, Michael Wiktowy wrote: > > I am finding this URI variable useful for past DBR retrieval but it is > > still not quite 100%. > > > > If the DBR site has any relative links in it (images), those links will > > still be > > looking for today's DBR and not the links relative to the date entered > > (i.e. is does not replace the document root with > > /pubkey/(date-in-hex)-site//). > > Perhaps there is a way for fproxy to prod the browser into redirecting to a > > new document root of the form 0xdate-site. > We discussed this. People wanted ?date= as a parameter.
I understand the value of having that as a human-readable parameter since it will be human entered. That I wouldn't want changed. However, as it is implemented now, it breaks any DBR links in the date-offsetted DBR freesite. It also seems to ignore any extra parameters that you want to put on (like ?htl= for instance ... so you can't retrieve a date shifted DBR if it is outside your default htl range). This certainly isn't a show-stopper bug but I thought that I would point it out anyways just in case there was a simple solution. The only one that I saw that didn't entail large amounts of inline html rewriting was sending a redirect to the browser to go to the absolute hex DBR address. However, that brings into question what happens when someone hits the "Yesterday's Edition" link in "Yesterday's Edition" of a freesite. Mike _______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
