Send me a specific example (the page contents in an attachment, or at least a
URL) and I'll take a look at it.
On Mon, Jun 11, 2001 at 01:02:48PM -0500, John Goerzen wrote:
> "David McNab" <[EMAIL PROTECTED]> writes:
>
> > 3) MIME Type Mis-Handling - when browsing
> > 'freenet:MSK@SSK@argargarg/
On Sun, Jun 10, 2001 at 07:20:02PM +1200, David McNab wrote:
> 1) Performance - I tried streaming an MP3 off Freenet, and ended up with
> ears full of stutter and gibberish.
> In contrast, a native binary version of FProxy, using FCP, delivered
> blissfully clean uninterrupted audio.
> I know my m
"David McNab" <[EMAIL PROTECTED]> writes:
> 3) MIME Type Mis-Handling - when browsing
> 'freenet:MSK@SSK@argargarg/sitename//', FProxy doesn't send any
> 'Content-Type: text/html' header back to the browser. This causes browser to
> mistake the default freesite page as something requiring downloa
On Sun, Jun 10, 2001 at 07:20:02PM +1200, David McNab wrote:
> I was willing to put up with FProxy up till now, and passively accept it as
> the 'Official Freenet HTTP Interface'.
> I suggest that a strategic decision be made to switch to native binary
> implementations of FProxy.
> On Windows, n
I was willing to put up with FProxy up till now, and passively accept it as
the 'Official Freenet HTTP Interface'.
But three things have convinced me that it needs to immediately take Tim
McVeigh's place on death row:
1) Performance - I tried streaming an MP3 off Freenet, and ended up with
ears
