Re: [Simple] NOTIFY without message-body

[Alex Audu <alex.audu at alcatel.com>]

Hi Jonathan, Paul,

According to the following, rfc 2045 defines a default content type of  
text/plain; charset=us-ascii

Cheers,
Alex.

===========================================================================
RFC 2045                Internet Message Bodies            November 1996


5.2.  Content-Type Defaults

  Default RFC 822 messages without a MIME Content-Type header are taken
  by this protocol to be plain text in the US-ASCII character set,
  which can be explicitly specified as:

    Content-type: text/plain; charset=us-ascii

  This default is assumed if no Content-Type header field is specified.
  It is also recommend that this default be assumed when a
  syntactically invalid Content-Type header field is encountered. In
  the presence of a MIME-Version header field and the absence of any
  Content-Type header field, a receiving User Agent can also assume
  that plain US-ASCII text was the sender's intent.  Plain US-ASCII
  text may still be assumed in the absence of a MIME-Version or the
  presence of an syntactically invalid Content-Type header field, but
  the sender's intent might have been otherwise.

====================================================================

Paul Kyzivat wrote:

> Jonathan Rosenberg wrote:
>
> > Paul Kyzivat wrote:
> >
> > > Jonathan,
> > >
> > > What you suggest is plausible, but I don't recall ever seeing 
> > > anything written that discusses the meaning of a Content-Type with 
> > > an empty body.
> > >
> > > That logic would imply that there is (conceptually) a special 
> > > content type for which an empty body is valid and a non-empty body 
> > > is not, and that this is a default content-type when the body is empty.
> >
> >
> > I don't see how you would come to this conclusion. There is no 
> > default value for Content-Type.
>
>
> This is probably just splitting hairs, and not worth discussion.
>
> > > I believe I have seen stacks that considered the presence of a 
> > > content type header invalid if there is no body. At the least there 
> > > ought to be something that says this is valid usage.
> >
> >
> >
> > It is written, in RFC 3261, section 20.15:
> >
> > 20.15 Content-Type
> >
> >    The Content-Type header field indicates the media type of the
> >    message-body sent to the recipient.  The "media-type" element is
> >    defined in [H3.7].  The Content-Type header field MUST be present if
> >    the body is not empty.  If the body is empty, and a Content-Type
> >    header field is present, it indicates that the body of the specific
> >    type has zero length (for example, an empty audio file).
>
>
> OK - I didn't remember that was there.
>
>     Paul
>
>
> _______________________________________________
> Simple mailing list
> Simple at ietf.org
> https://www1.ietf.org/mailman/listinfo/simple



_______________________________________________
Simple mailing list
Simple at ietf.org
https://www1.ietf.org/mailman/listinfo/simple