reSIProcate

Mailing Lists

Source Code

Google Search:



< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate] Bug in DateCategory::parse()

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@xxxxxxxxxxxxxx <mailto:mdill@xxxxxxxxxxxxxx>> 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@xxxxxxxxxxxxxxxxxxx
    <mailto:resiprocate-devel@xxxxxxxxxxxxxxxxxxx>
    https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel


------------------------------------------------------------------------

_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel