Message-Id: <firstname.lastname@example.org> Date: Thu, 10 Jul 1997 09:41:51 -0400 To: email@example.com From: Greg Marr <firstname.lastname@example.org> Subject: Re: An smtp URL scheme In-Reply-To: <email@example.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 At 10:04 PM 7/9/97 -0700, Walter Ian Kaye wrote: >At 9:51a -0400 07/09/97, Greg Marr wrote: > > However, the preferred way is > > smtp://host/user?subject=subject+body=yes+X-header=header > >This makes no sense. CGI's expect ampersands as delimiters. Except for the ones that expect +'s. with an encoding type of x-www- encoded or something like that instead of x-url-encoded. There was an entire thread or two about this on one of the mailing lists I am on a while ago. I'll have to track it down sometime. I didn't invent this, I highly double that Richard Levitte and I both invented the same syntax out of thin air. > > because otherwise the URL should be encoded to: > > smtp://host/user?subject=subject&body=body&X- header=header > > when it is included in an HTML page. > >No, you are confusing rendered text with attribute values. How am I confusing rendered text with attribute values? Are you saying that entity replacement shouldn't be performed on attribute values? -----BEGIN PGP SIGNATURE----- Version: PGP for Personal Privacy 5.0 Charset: noconv iQA/AwUBM8TmngtYMjJ37cDeEQILLQCeMNbdB69qK1d2JquwilJ2HMH43OAAoIDn U8cpzovbEoyh6rUJGUjAsGcz =N9ur -----END PGP SIGNATURE----- -- Greg Marr firstname.lastname@example.org "We thought you were dead." "I was, but I'm better now." - Sheridan, "The Summoning"