Re: [BUG] wsp_headers.c, header's handling in Connect PDU

Yes.
WSP 8.4.1.2 Field values:

first octet in all the field values can be interpreted as follows:

0 - 30 : This octet is followed by the indicated number (0 –30) of data octets,

So 0 is included in this range.

So in mean of general WSP encoding everything is ok.
But of course, Nokia send malformed Accept header:

( 8.4.2.7 Accept field
The following rules are used to encode accept values.
Accept-value = Constrained-media | Accept-general-form
Accept-general-form = Value-length Media-range [Accept-parameters]
Media-range = (Well-known-media | Extension-Media) *(Parameter)
Accept-parameters = Q-token Q-value *(Accept-extension)
Accept-extension = Parameter
Constrained-media = Constrained-encoding
Well-known-media = Integer-value
; Both are encoded using values from Content Type Assignments table in Assigned 
Numbers
Q-token = <Octet 128> )

And we have: Accept-general-form => Value-length Media-range [Accept-parameters]
So value-length is 0 and Media-range is absent.

So we have 2 options:
1) Say to Nokia 3660 users - sorry, your phone doesn't work with our
WAP gw
2) Patch wap gateway to skip this faulty Accept header and process rest
headers.

Stipe Tolj wrote:
> can you point us directly to the section of the WSP spec where you
> "see" that a WSP header may be empty, hence with 0x00 as value?!
> 
> Stipe
> 

-- 
Vjacheslav Chekushin                                mailto:[email protected]
Latvian Mobile Phone Company                        http://www.lmt.lv