Re: Quoted-string type in wap/wsp_headers.c

Paul Bagyenda wrote:

> Actually this fix had been proposed a while back, but somehow it seems 
> never to have made it into the code (although the other fixes did). I 
> quote: http://www.mail-archive.com/[email protected]/msg02493.html
> 
> On Mar 15, 2005, at 00:46, Jonathan Houser wrote:
> 
>>
>>       Søren,
>>
>>> No, it's not in the WAP headers, but is that an excuse for not sticking
>>> to the standard? Besides, who's to tell when some device uses it in the
>>> WAP headers?
>>
>>
>>      Hey, I didn't write Kannel.  I was just saying that if it's in 
>> the MMS headers themselves, then Kannel's not the issue.  In my MMSC I 
>> fully support quoted-string's.  It's not like it's hard or anything.  
>> If it starts with 0x22 (I think it was 0x22) then it's quoted, strip 
>> the quote and move on parsing the string.  Fix it in Kannel and submit 
>> it as a patch and I'm sure they'll apply it.  You are correct, it's in 
>> the specs and should be supported.

now, catching up with the list again ;)

I see that Aarno did commit your patch, and it's in revision 1.17 of 
wap/wsp_headeer.c.

Then, in revision 1.18, I pulled it off again via this ChangeLog entry:

[...] Along with this Aarno did
       break the quoted parameter parsing within revision 1.17. Reverting this
       back to the previous behaviour to make test/test_headers.c happy again.

Actually I can't recall anymore, but I'm investigating. Why did I roll back?

Stipe

mailto:stolj_{at}_wapme.de
-------------------------------------------------------------------
Wapme Systems AG

Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany

phone: +49.211.74845.0
fax: +49.211.74845.299

mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
-------------------------------------------------------------------