Re: Majordomo drops multi-line Subject:

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Guido Neitzer <guido(dot)neitzer(at)pharmaline(dot)de>
Cc: General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Majordomo drops multi-line Subject:
Date: 2006-08-23 14:51:33
Message-ID: 20060823145133.GM1963@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Guido Neitzer wrote:

> ----8<--------8<--------8<--------8<--------8<--------8<----
> 2.2.1. Unstructured Header Field Bodies
>
>
> Some field bodies in this standard are defined simply as
> "unstructured" (which is specified below as any US-ASCII characters,
> except for CR and LF) with no further restrictions. These are
> referred to as unstructured field bodies. Semantically,
> unstructured
> field bodies are simply to be treated as a single line of characters
> with no further processing (except for header "folding" and
> "unfolding" as described in section 2.2.3).
>
> ----8<--------8<--------8<--------8<--------8<--------8<----

So see what "folding" means. Section 2.2.3 says

2.2.3. Long Header Fields

Each header field is logically a single line of characters comprising
the field name, the colon, and the field body. For convenience
however, and to deal with the 998/78 character limitations per line,
the field body portion of a header field can be split into a multiple
line representation; this is called "folding". The general rule is
that wherever this standard allows for folding white space (not
simply WSP characters), a CRLF may be inserted before any WSP. For
example, the header field:

Subject: This is a test

can be represented as:

Subject: This
is a test

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bernhard Weisshuhn 2006-08-23 14:51:47 Re: Majordomo drops multi-line Subject:
Previous Message Tom Lane 2006-08-23 14:50:46 Re: error msg when pg_restore