Wireshark · Ethereal-users: [Fwd: Re: [Ethereal-dev] Re: [Ethereal-users] Decoding SIP problem]

[Lars Roland <lars.roland@xxxxxxx>]

Forward also to Users-List:

-------- Original Message --------
Subject: Re: [Ethereal-dev] Re: [Ethereal-users] Decoding SIP problem
Date: Wed, 03 Nov 2004 12:28:34 +0100
From: Lars Roland <lars.roland@xxxxxxx>
Reply-To: Ethereal development <ethereal-dev@xxxxxxxxxxxx>
To: martin.regner@xxxxxxxxx,	Ethereal development 
<ethereal-dev@xxxxxxxxxxxx>
References: <20041103103840.MFPE29770.amsfep20-int.chello.nl@localhost>

Hello,

you are right, sorry.
I mixed it up with the Header Field Format (Section 7.3.1, RFC 3261)
The Request Line and the Status Line doens't allow multiple spaces.
Thus Ethereal is right this time and rejects the message, because it is
violating the standard.
However Ethereal's parser for the Header Fields should be improved to
allow multiple spaces and tabs.
The SIP dissector already contains "TODO" comments for this.

Regards,
Lars

martin.regner@xxxxxxxxx wrote:
> Andres Broman wrote:
>
> > RFC3261 says:
> > Request-Line   =  Method SP Request-URI SP SIP-Version CRLF
> >
> > Does this realy allow multiple SP ?
> > Best regards
> > Anders
>
>
> If it had said 1*(SP) then it would have been allowed to have more than one space character,
> but the ABNF doesn't allow more than one SP in this case what I can see.
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev

_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev