On Thu, 6 Aug 2009 11:04:07 -0400, Evan Daniel wrote: > On Thu, Aug 6, 2009 at 7:08 AM, Matthew > Toseland<[email protected]> wrote: > > On Tuesday 04 August 2009 05:29:35 Dennis Nezic wrote: > >> For the past few Freenet builds, fproxy's behavior has changed > >> whereby it seems to use http "301 Moved Permanently" to redirect > >> downloads of the form 'http://localhost:8888/c...@../filename' to > >> 'freenet:c...@..' ... but it doesn't seem to include the filename > >> part in the redirected location ... or at least when I 'wget' CHKs > >> it doesn't include the filenames .... it uses the CHK as the > >> filename :\. > > > > I don't think that's new. If the CHK doesn't include the filename > > as metadata, we redirect it; that's been true for ages. > > The problem is that I think Frost has a habit of inserting files > without a filename (to generate the same CHK), and then inserting > another CHK with a filename that redirects to it. Or something > equally weird, I'm not clear on the details. The problem it's trying > to solve is that the same file with different names should collide > (not an uncommon case in the filesharing world).
In that case, in the absence of a filename in the redirected location, freenet should fallback to the originally suggested one. (On a not entirely unrelated note, is it possible to disable fproxy's warning about "dangerous" mimetypes (pdfs, zips, etc) -- maybe have a "do not warn me again" button -- since, again, it breaks wget. Or at least issue an appropriate HTTP response code like "permission denied" or something so wget doesn't think that the fproxy html warning page is the actual pdf file. Fproxy should be an http proxy, not a browser ui :P.) _______________________________________________ Support mailing list [email protected] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[email protected]?subject=unsubscribe
