Date: Thu, 21 Mar 2002 15:31:33 -0500
From: Aaron Angel <aangel@myrealbox.com>
To: gopher@complete.org
Subject: [gopher] Re: Existing \n.\n behavior
Message-ID: <20020321153133.A21542@daemon.infoarc.sodaknet.com>
Mail-Followup-To: gopher@complete.org
References: <B4C8D7BA-3CD7-11D6-B325-0003930BF072@complete.org>
Mime-Version: 1.0
Content-type: text/plain
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <B4C8D7BA-3CD7-11D6-B325-0003930BF072@complete.org>;
 from jgoerzen@complete.org on Thu, Mar 21, 2002 at 09:27:00AM -0500
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

A few added notes, mostly regarding IE6.

On Thu, Mar 21, 2002 at 09:27:00AM -0500, John Goerzen wrote:
> 
> Testing \n.\n in the middle of a file
> -------------------------------------
> Clients:
>    [...]
>    IE 5.1/mac: aborts transfer at \n.\n

IE 6 ignores the \n.\n rule altogether, it seems.

> 
> Testing \n.\n at the end of a file
> ----------------------------------
> Clients:
>    [...]
>    IE: strips it

IE 6, ignoring the rule, doesn't strip it.

> 
> Testing no \n.\n at all
> -----------------------
> Clients:
>    [...]
>    IE: no problems

Likely the same with 6, but I can't really tell.

> 
> UMN gopherd server behavior
> ---------------------------
>    Normal file (no \n.\n in it): adds \n.\n at end
>    File with \n.\n in middle: passes it through, adds \n.\n at end
>    File with \n.\n at the end: passes it through, adds another \n.\n

I believe bucktooth doesn't have any odd quirks with these
circumstances either.

-- 
Stop Policeware.  www.stoppoliceware.org
-- Attached file included as plaintext by Ecartis --

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
MessageID: h4+nsnI/aTyuU9gjgdxpqmw3kv0oCKAw

iQA/AwUBPJpDJPm2Eo63Q7FxEQKiCwCfXu/zh519iFU/PI+/8lCM9RGsbq8AoLbZ
EY3ZP50skqm6iaHp76kxf2/8
=OTAE
-----END PGP SIGNATURE-----