Re: PKIX-2 http

[Peter Williams <peter@xxxxxxxxxxxx>]

Anil R. Gangolli wrote:

> Peter Williams wrote:
> >
> > We do need to agree the mime type for returning an http resource,
> > still.
> >
> > I note that the introduction also allows the http mechanism to be used
> > for pushing the cert/CRL to the directory. Perhaps its best
> > that the objects we are pulling/pushing are indeed simply
> > regarded as files. When pulling a .crt file the object
> > is labelled application/octet-string. When pushing files,
> > the file objects are transferred in a classical http push operation's
> > multipart mime type.
> >
>
> Most HTTP clients that I know about use the mime type to
> dispatch to type-specific handling code.  Using a generic
> mime type like application/octet-string precludes this.
>
> For certificates and CRLs browsers do and will likely continue
> to use MIME types that indicate both the type and often
> an application-specific usage.
>
> Examples are:
>
> application/x-x509-user-cert
> application/x-x509-ca-cert


Anil,

you and I and Microsoft have all suggested this; but there
is just silence. Somehow, this simple statement just
will not get written down and become what we
all use. I know not why this issue fails to get
resolved.

In lieu of other progress, I fell back to what I
hoped I could get actually written, and I started
with the simplest type of all....

application/octet-string; name=foo.crt
application/octet-string; name=foo.crl

Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Peter Williams
Content-Disposition: attachment; filename="vcard.vcf"

Attachment converted: Lutefisk:vcard.vcf 16 (TEXT/R*ch) (0001C17E)