|
Content-Type: |
TEXT/PLAIN; charset=US-ASCII; format=flowed |
Sender: |
|
Subject: |
|
From: |
|
Date: |
Thu, 15 Jun 2006 23:53:57 -0400 |
In-Reply-To: |
<Pine.GSO.4.44.0606151948040.1930-100000@infinity> |
MIME-Version: |
1.0 |
Reply-To: |
|
On Thu, 15 Jun 2006, Winship wrote:
> But that is not what is sent, which is INFOLSTOWN-L
> That is not a command, so you get back an error message. There should be
> a space there, INFO LSTOWN-L not INFOLSTOWN-L .
This is behavior is seen in Pine, though the way LISTSERV handles it is
not in spec. The rfc2369 header information refers to RFC1738 -- which
requires the space character to be encoded as "%20" in the URL.
From RFC2369 (2):
The list header fields are subject to the encoding and character
restrictions for mail headers as described in [RFC822]. Additionally, the
URL content is further restricted to the set of URL safe characters
[RFC1738].
from RFC1738 (2.2):
The space character is unsafe because significant spaces may disappear and
insignificant spaces may be introduced when URLs are transcribed or
typeset or subjected to the treatment of word-processing programs.
All unsafe characters must always be encoded within a URL.
When the header is corrected to have the space encoded as "%20" Pine
handles it fine.
-- DCP
|
|
|