# Re: gopher URLs (was Re: how to make progress ...)

Mark P. McCahill (mpm@boombox.micro.umn.edu)
Wed, 23 Mar 94 09:37:26 CST

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Tim Berners-Lee: "Re: how to make progress on the URL document"
- Previous message: dob@inel.gov: "Re: gopher URLs (was Re: how to make progress ...)"
- Maybe in reply to: Keith Moore: "gopher URLs (was Re: how to make progress ...)"
- Next in thread: Mark P. McCahill: "Re: gopher URLs (was Re: how to make progress ...)"

    Date: Wed, 23 Mar 94 09:37:26 CST

    Message-Id: <9403231537.AA02253@boombox.micro.umn.edu>

    From: "Mark P. McCahill" <mpm@boombox.micro.umn.edu>

    To: moore@cs.utk.edu

    Subject: Re: gopher URLs (was Re: how to make progress ...)

In message <199403230212.VAA08254@wilma.cs.utk.edu> Keith Moore writes:
> shouldn't the gopher URL spec say something to the effect
> that the client shouldn't allow gopher URLs with embedded
> newlines or tabs?
>
> (to keep gopher URLs from being used to spoof other protocols)
>

I must be a little slow this morning, because I don't understand what you
are saying. How exactly might a gopher URL be used to spoof other protocols?
Can you write up a concrete example of what you are trying to avoid so I
can be sure I understand what you are talking about?

You should also write up the wording you propose to add to address this
issue... since I don't know what you are talking about I can't figure out
how to rewrite the spec.

Mark P. McCahill

gopherspace engineer/University of Minnesota
mpm@boombox.micro.umn.edu
612 625 1300 (voice) 612 625 6817 (fax)

- Next message: Tim Berners-Lee: "Re: how to make progress on the URL document"
- Previous message: dob@inel.gov: "Re: gopher URLs (was Re: how to make progress ...)"
- Maybe in reply to: Keith Moore: "gopher URLs (was Re: how to make progress ...)"
- Next in thread: Mark P. McCahill: "Re: gopher URLs (was Re: how to make progress ...)"