Evan Daniel skrev:
On Wed, Nov 18, 2009 at 9:17 PM, Dennis Nezic
<denn...@dennisn.dyndns.org> wrote:
Hrrm. I'm no expert, but doesn't the "/freenet:u...@..." URL syntax seem
wrong? The protocol should be the first thing, not in the pathname? And
it would only make sense if it was from some external non-fproxy
source, no? I mean, if the user is already accessing fproxy, what's the
point of freenet: references?
It seems to me that having fproxy automatically redirect
all /USK@ /CHK@ /SSK@ links to /freenet:USK@ links is pointless in the
first place ... and getting rid of this redirection should solve the
problem and simplify things too :).
No, the / at the beginning is perfectly correct.
Your browser has no clue how to handle a freenet: URL. The / at the
front means it should use that as an absolute path to construct an
http: URL from, using the current server (typically 127.0.0.1:8888).
FProxy provides a translation layer that gets the corresponding
freenet: URL over http in that format.
The proper URL of a Freenet document is not "u...@blah" or
"http://127.0.0.1:8888/u...@blah"; or even
"http://127.0.0.1:8888/freenet:u...@blah";. It's "freenet:u...@blah".
The http version is simply a translation that your browser (and wget,
etc) knows what to do with.
URLs are supposed to begin with a protocol: identifier. Including
only a portion of the correct URL in the translation layer, while not
exactly wrong, seems silly. The proper solution is to make sure that
all http: URLs for Freenet documents follow the same format. As long
as that format is consistent, I don't think there's any problem with
wget and such.
Yes, but that contradicts putting a slash /before/ the protocol identifier.
_______________________________________________
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
