Re: [Users] x-wap-profile missing/required

2006-05-15 Thread Paul Bagyenda
Yes there is a way and in fact it is in there IMO, however obviously  
along the way a bug crept in. If the wap-profile URL is missing,  
Mbuni uses the HTTP Accept headers to try and find a reasonable  
compromise. I will do a fix and update.

P.

On May 15, 2006, at 19:34, Deon van der Merwe wrote:

 Hi,

 We are tracing a problem with a Motorola V3i submitting a message to
 mbuni.  Thing is that the phone does not include the x-wap-profile
 HTTP header.  So: the phone must be broken!!!  Reading the specs [ETSI
 TS 126 234 V6.6.0 (2005-12)], it turns out (to my surprise) that the
 x-wap-profile is not a required header.
 quote
 5.2.5 Signalling of profile information between client and server
 When a PSS client or server support capability exchange it shall
 support the profile information transport over both HTTP and RTSP
 between client and server as defined in clause 9.1 (including its
 subsections) of the WAP 2.0 UAProfspecification [40] with the
 following additions:
 - The x-wap-profile and x-wap-profile-diff headers may not be
 present in all HTTP or RTSP request. That is, the requirement to send
 this header in all requests has been relaxed.
 /quote

 Here is how mbuni fails:
 2006-05-15 17:54:14 [23380] [0] PANIC: gwlib/octstr.c:2340:
 seems_valid_real: Assertion `ostr-len + 1 = ostr-size' failed.
 (Called from gwl
 ib/octstr.c:1310:octstr_strip_nonalphanums.)
 2006-05-15 17:54:14 [23380] [0] PANIC:
 /usr/local/bin/mmsproxy(gw_panic+0x175) [0x8085dba]
 2006-05-15 17:54:14 [23380] [0] PANIC: /usr/local/bin/mmsproxy  
 [0x808d341]
 2006-05-15 17:54:14 [23380] [0] PANIC:
 /usr/local/bin/mmsproxy(octstr_strip_nonalphanums+0x2c) [0x808aa11]
 2006-05-15 17:54:14 [23380] [0] PANIC:
 /usr/local/bin/mmsproxy(main+0x24c) [0x8052afc]
 2006-05-15 17:54:14 [23380] [0] PANIC:
 /lib/libc.so.6(__libc_start_main+0xab) [0x4035144b]
 2006-05-15 17:54:14 [23380] [0] PANIC: /usr/local/bin/mmsproxy  
 [0x80527b1]


 This is where it goes wrong:
h.vasp = NULL;
h.profile_url = NULL;
h.ua = http_header_value(h.headers, octstr_imm(User- 
 Agent));
/* Get the profile URL and store it. Has effect of
 fetching if missing. */
if ((h.profile_url = http_header_value(h.headers,

 octstr_imm(X-Wap-Profile))) == NULL)
 h.profile_url = http_header_value(h.headers,
 octstr_imm(Profile));
octstr_strip_nonalphanums(h.profile_url);

 So, is there any way in which we can include a default profile into
 the configuration?
 Or, maybe someone else has a better option/solution?

 ___
 Users mailing list
 Users@mbuni.org
 http://mbuni.org/mailman/listinfo/users_mbuni.org


___
Users mailing list
Users@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org


Re: [Users] x-wap-profile missing/required

2006-05-15 Thread Paul Bagyenda
fixed hopefully in CVS. Please let me know.
On May 15, 2006, at 19:34, Deon van der Merwe wrote:

 Hi,

 We are tracing a problem with a Motorola V3i submitting a message to
 mbuni.  Thing is that the phone does not include the x-wap-profile
 HTTP header.  So: the phone must be broken!!!  Reading the specs [ETSI
 TS 126 234 V6.6.0 (2005-12)], it turns out (to my surprise) that the
 x-wap-profile is not a required header.
 quote
 5.2.5 Signalling of profile information between client and server
 When a PSS client or server support capability exchange it shall
 support the profile information transport over both HTTP and RTSP
 between client and server as defined in clause 9.1 (including its
 subsections) of the WAP 2.0 UAProfspecification [40] with the
 following additions:
 - The x-wap-profile and x-wap-profile-diff headers may not be
 present in all HTTP or RTSP request. That is, the requirement to send
 this header in all requests has been relaxed.
 /quote

 Here is how mbuni fails:
 2006-05-15 17:54:14 [23380] [0] PANIC: gwlib/octstr.c:2340:
 seems_valid_real: Assertion `ostr-len + 1 = ostr-size' failed.
 (Called from gwl
 ib/octstr.c:1310:octstr_strip_nonalphanums.)
 2006-05-15 17:54:14 [23380] [0] PANIC:
 /usr/local/bin/mmsproxy(gw_panic+0x175) [0x8085dba]
 2006-05-15 17:54:14 [23380] [0] PANIC: /usr/local/bin/mmsproxy  
 [0x808d341]
 2006-05-15 17:54:14 [23380] [0] PANIC:
 /usr/local/bin/mmsproxy(octstr_strip_nonalphanums+0x2c) [0x808aa11]
 2006-05-15 17:54:14 [23380] [0] PANIC:
 /usr/local/bin/mmsproxy(main+0x24c) [0x8052afc]
 2006-05-15 17:54:14 [23380] [0] PANIC:
 /lib/libc.so.6(__libc_start_main+0xab) [0x4035144b]
 2006-05-15 17:54:14 [23380] [0] PANIC: /usr/local/bin/mmsproxy  
 [0x80527b1]


 This is where it goes wrong:
h.vasp = NULL;
h.profile_url = NULL;
h.ua = http_header_value(h.headers, octstr_imm(User- 
 Agent));
/* Get the profile URL and store it. Has effect of
 fetching if missing. */
if ((h.profile_url = http_header_value(h.headers,

 octstr_imm(X-Wap-Profile))) == NULL)
 h.profile_url = http_header_value(h.headers,
 octstr_imm(Profile));
octstr_strip_nonalphanums(h.profile_url);

 So, is there any way in which we can include a default profile into
 the configuration?
 Or, maybe someone else has a better option/solution?

 ___
 Users mailing list
 Users@mbuni.org
 http://mbuni.org/mailman/listinfo/users_mbuni.org


___
Users mailing list
Users@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org


Re: [Users] x-wap-profile missing/required

2006-05-15 Thread Deon van der Merwe
Hi Paul,

On 5/15/06, Paul Bagyenda [EMAIL PROTECTED] wrote:
 fixed hopefully in CVS. Please let me know.

yup- it is working.  Thanks allot Paul.

___
Users mailing list
Users@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org