# Splitting a URL over multiple lines

Paul Hoffman, Gopher/Web maintainer (goph-mn@proper.com)
Thu, 24 Nov 1994 16:39:37 -0800

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Jon P. Knight: "Re: Splitting a URL over multiple lines"
- Previous message: Roy T. Fielding: "Re: I-D proposing new Z39.50 URL"
- Next in thread: Jon P. Knight: "Re: Splitting a URL over multiple lines"
- Reply: Jon P. Knight: "Re: Splitting a URL over multiple lines"

    Message-Id: <aafad549010210035893@[165.227.40.14]>

    Date: Thu, 24 Nov 1994 16:39:37 -0800

    To: uri@bunyip.com

    From: goph-mn@proper.com (Paul Hoffman, Gopher/Web maintainer)

    Subject: Splitting a URL over multiple lines

In looking at the most recent URL spec, I did not see any mention of the
possibility of splitting a URL with carriage returns. For example, some
URLs could be more than 80 characters and some display systems would
therefore truncate them, rendering them useless. One could arbitrarily
split a URL in the middle to prevent such truncation or simply to make it
more readable by humans.

Because an interal carriage return would never be misinterpreted (by
definition, a real carriage return in the URL would have to be encoded as
"%0D"), I would think that an interal carriage return would be harmless.
However, that doesn't mean that it is allowed.

Is it harmless? Should it be allowed?

--Paul Hoffman
--Proper Publishing

- Next message: Jon P. Knight: "Re: Splitting a URL over multiple lines"
- Previous message: Roy T. Fielding: "Re: I-D proposing new Z39.50 URL"
- Next in thread: Jon P. Knight: "Re: Splitting a URL over multiple lines"
- Reply: Jon P. Knight: "Re: Splitting a URL over multiple lines"