[reSIProcate] Bug in DateCategory::parse()
Martin Dill
mdill at newheights.com
Fri Dec 2 22:05:30 CST 2005
Yes you are right. I had only looked section 20.17 of the rfc, and not
at 25.1 where the format is actually specified. My mistake!
Adam Roach wrote:
> That's my reading of it also. Per spec, the header that is causing it
> to throw an exception is malformed.
>
> That said, Postel's Maxim would certainly support the idea of changing
> the code so that it parses headers without the "wkday" portion.
> Without looking at the parsing code specific to the date header field,
> I would guess that doing so should be a relatively trivial effort.
>
> /a
>
> david Butcher wrote:
>
>> My read of RFC3261 has the week day mandatory.
>>
>> rfc1123 <http://www.faqs.org/rfcs/rfc1123.html>-date = wkday "," SP
>> date1 SP time SP "GMT"
>>
>> Robert?
>>
>> david
>>
>>
>>
>> On 12/1/05, *Martin Dill* <mdill at newheights.com
>> <mailto:mdill at newheights.com>> wrote:
>>
>> Hi,
>> There appears to be a bug in DateCategory::parse().
>> As far as I can tell, it assumes that the date it is given will
>> always be in
>> the form 'Mon, 04 Nov 2002 17:34:15 GMT'. However, I think this is
>> incorrect. According to RFC822, the day part is optional. When
>> resip is
>> given a date in the form '04 Nov 2002 17:34:15 GMT', without the
>> day part,
>> it fails with an exception of 'parsebuffer.cxx:78, Parse failed
>> skipped over
>> eof in context: Date'.
>>
>> Can someone verify this?
>>
>> Thanks
>> Martin Dill
>> NewHeights Software
>>
>> _______________________________________________
>> resiprocate-devel mailing list
>> resiprocate-devel at list.sipfoundry.org
>> <mailto:resiprocate-devel at list.sipfoundry.org>
>> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> resiprocate-devel mailing list
>> resiprocate-devel at list.sipfoundry.org
>> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>>
>
>
More information about the resiprocate-devel
mailing list