[Serdev] PA module requires Accept header

[Jan Janak]

I don't think so. I saw references to the patch on the lists but could
not find it there. I recall that I received a patch to pa privately some
time ago, but I don't remember applying it.

  Jan.

On 15-06-2005 15:03, Klaus Darilion wrote:
> Hi!
> 
> I wonder if this patch ever submitted and commited into CVS?
> 
> regards,
> klaus
> 
> Gregory McGarry wrote:
> >I have a large patch to make the PA module RFC3265 and
> >RFC3903 compliant.
> >
> >Where can I forward the changes for inclusion?
> >
> >--
> >Xten Networks Inc.
> >www.xten.com 
> >
> >
> >>-----Original Message-----
> >>From: serdev-bounces at lists.iptel.org 
> >>[mailto:serdev-bounces at lists.iptel.org] On Behalf Of Alex
> >
> >Rootham
> >
> >>Sent: November 24, 2004 8:45 AM
> >>To: serdev at lists.iptel.org
> >>Subject: [Serdev] PA module requires Accept header
> >>
> >>Hi,
> >>
> >>The PA module seems to require that SUBSCRIBE messages
> >
> >have 
> >
> >>the Accept header on them (returns bad-message-error if
> >
> >it's 
> >
> >>not there), but the
> >>RFC3265 seems to say that this header is optional.  I
> >
> >think 
> >
> >>it's a good idea for clients to use the Accept header to 
> >>indicate the acceptable format of notify bodies, but
> >
> >strictly 
> >
> >>speaking, I believe it's not rfc-compliant...
> >>
> >>RFC3265
> >>3.1.3. Additional SUBSCRIBE Header Values
> >>
> >>  Because SUBSCRIBE requests create a dialog as defined
> >
> >in SIP [1],
> >
> >>  they MAY contain an "Accept" header.  This header, if
> >
> >present,
> >
> >>  indicates the body formats allowed in subsequent NOTIFY
> >
> >requests.
> >
> >>  Event packages MUST define the behavior for SUBSCRIBE
> >
> >requests
> >
> >>  without "Accept" headers; usually, this will connote a
> >
> >single,
> >
> >>  default body type.
> >>
> >>
> >>Alex Rootham
> >>Blueslice Networks
> >>
> >>
> >>_______________________________________________
> >>Serdev mailing list
> >>serdev at lists.iptel.org
> >>http://lists.iptel.org/mailman/listinfo/serdev
> >>
> >
> >
> >
> >_______________________________________________
> >Serdev mailing list
> >serdev at lists.iptel.org
> >http://lists.iptel.org/mailman/listinfo/serdev
> >
> >
> 
> _______________________________________________
> Serdev mailing list
> serdev at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serdev