>From "David McNab" <[EMAIL PROTECTED]>
>> I don't know if anyone has mentioned this Fproxy quirk: When you click on
>a
>> link to a file-type your browser doesn't know about, your node starts
>> downloading the file while your browser pops up a dialog asking if you
>want
>> to download it
>
>Fault of browser, not fproxy. Seems that the browser makes this decision
>based on the file extension of the URL.
>For instance,
>MSK@SSK@p0EFqjmDioSqKmYYORPrClUepi4QAgE/snarfoo//index.html
>causes a normal load of snarfoo's main page, while
>MSK@SSK@p0EFqjmDioSqKmYYORPrClUepi4QAgE/snarfoo//
>causes the download dialog to pop up, because as far as the browser's
>concerned, the incoming data ain't html. Seems the browser ignores the
>'content-type' coming back in the reply header.
>
>This is probably why it's become standard practice for freesite links to
>include the default page. This needs to go into the list of 'good freesite
>design tips', if there is such a list.
>
>I can't see any workaround for this within FProxy.
>
>David
>
It's very common for http websites to have pages ending in '/'... is it the
double-slash that's confusing the browser, or what?
--
Benjamin Coates
_______________________________________________
Devl mailing list
[EMAIL PROTECTED]
http://lists.freenetproject.org/mailman/listinfo/devl
