header name.
aarno
On Wednesday, December 4, 2002, at 12:01 PM, Claudio Montanari wrote:
Well, I spent a while to "decipher" the standard and I am "quite" sure the no-cache value is a long integer.
I wish to share with you my interpretation of the spec WAP-230-WSP-20010705-a:
According to chap.8.4.2.1 "Basic Rules" short integers are in the range 0-127 and should be encoded "1xxxxxxx".
According to chap. 8.4.2.15 "Cache-Control Field" the no-cache value is <Octet 128>, expecting to be a long integer because out of the 0-127 range.
As a consequence the Long Integer = Short-Length Multi-octet-integer --> 8180
But this is just my interpretation.
Please, let me know where I am wrong and thank you for your comment.
Bye, Claudio,
-----Messaggio originale-----
Da: Aarno Syvänen [mailto:[EMAIL PROTECTED]]
Inviato: mercoledì 4 dicembre 2002 11.30
A: Claudio Montanari
Cc: 'Chris Wilson'; [EMAIL PROTECTED]
Oggetto: Re: R: Setting No Cache in WAP Push
Yeah, expect no-cache is a short integer, so value-length is not needed.
Aarno
On Wednesday, December 4, 2002, at 11:00 AM, Claudio Montanari wrote:
In my understanding you should add a Cache-Contol http header to the push message header.
According to "WAP-230-WSP"
01 Transaction ID (Push ID)
06 PDU Type (Push PDU)
18 Header Length (24 bytes)
AE Content Type=application/vnd.wap.sic (0x80 | 0x2E)
88 Cache-Control= (encoding v.1.1 table 39)
81 Next is 1-octet Integer Value > 127
80 No-Cache (octet 128) (chap. 8.4.2.15)
96 Host (0x80 | 0x16), WAP - 230, Appendix A, table 39 (wsp)
6C 6F 63 61 6C 68 6F 73 74 3A 38 30 38 30 localhost:8080
00
8D Content-Length (wsp, table 39)
DD 221 bytes
B4 Push-Flag (wsp, table 39)
80 no flags set (wsp, chapter 8.4.2.59 & chapter 8.4.2.1; SPEC-PushOTA-19991108)
....
As an alternative, could be easier to control the phone cache by the WML deck you send with the Service Indication.
If you want to be sure the page is newly loaded every time it is displayed, you should use the meta tags
<meta http-equiv="Cache-control" content="no-cache" forua="true"/>
in the <head> section of the WML deck file.
In this case, you would take into account the different behavior of the micro browser in the mobile phone in respect of the cache management.
I send this reply to the list just to have comments about it.
Bye, Claudio.
-----Messaggio originale-----
Da: Chris Wilson [mailto:[EMAIL PROTECTED]]
Inviato: martedì 3 dicembre 2002 18.34
A: [EMAIL PROTECTED]
Oggetto: Setting No Cache in WAP Push
Hi, I saw a post you had shown below.
I am interested in what would have to be added to the message described below to set NO-CACHE in the HTTP header. I looked in the document "WAP-230-WSP-20010705-a.pdf Page 86" but I was unable to determining how to fill in the CACHE fields. Basically the problem I am running into is when a phone gets my WAP push it will execute the link I send the first time. If the user trys to execute that link again it uses it's local cache instead of requesting from the server again.
Here is an example of what I am trying to encode:
0x00, // Transaction ID (Push ID)
0x06, // PDU Type (Push PDU) Apndx A Table 34
0x01, // Header Length (not sure why this is one)
(byte)0xAE, // Content Type=application/vnd.wap.sic (0x80 | 0x2E)
0x02, // <Version number - WBXML version 1.2>
0x05, // <SI 1.0 Public Identifier>
0x6A, // <Charset=UTF-8 (MIBEnum 106)> WAP-230 table 42
0x00, // <String table length>
0x45, // <SI element start, with content 0x05 | 0x40>
(byte)0xC6, // <indication element start, with content and attributes 0x06 | 0x40>
0x0C, // (0C http://)
0x03 // next is an ASCII string 0x00 terminated
~~~~~~~~~
<URL LINK>
<String Description of URL>
I appreciate any enlightenment you can send my way.
-- Chris
--------------------------------------------------------------------
http://www.mail-archive.com/users@kannel.3glab.org/msg02194.html
Claudio Montanari
TAI S.r.l.
Viale Gramsci 12 - 56125 - Pisa
Via Pazzagli 2 - 50141 - Firenze
Tel: +39 050 503222
Fax. +39 050 24421
E-mail: [EMAIL PROTECTED]
http://www.tai.it
00 Default SMSC
51 UDHI and SUBMIT
00 MR
0C Destination number length (12 digits)
91 Destination number format (international)
xxxxxxxxxxxx Destination number (xxxxxxxxxxxx)
00 Protocol ID
04 Data Coding Schema (DCS 8-bit encoded)
A7 Validity Period (24 h)
7C User Data Length (124 bytes)
06 User Data Header Length (6 bytes)
05 UDH Item Element id (Port Numbers)
04 UDH IE length (4 bytes)
0B84 destination port number
23F0 origin port number
01 Transaction ID (Push ID)
06 PDU Type (Push PDU)
15 Header Length (21 bytes)
AE Content Type=application/vnd.wap.sic (0x80 | 0x2E)
96 Host, WAP - 230, Appendix A, table 39 (wsp)
6C 6F 63 61 6C 68 6F 73 74 3A 38 30 38 30 localhost:8080
00 End of the text string (wsp, chapter 8.4.2.29 & chapter
8.4.2.1)
8D Content-Length (wsp, table 39)
DD in hex, 221 bytes (wsp, chapter 8.4.2.20 & chapter
8.4.2.1)
B4 Push-Flag (wsp, table 39)
80 no flags set (wsp, chapter 8.4.2.59 & chapter
8.4.2.1; SPEC-PushOTA-19991108.
chapter 9.1.3)
02 <Version number - WBXML version 1.2>
05 <SI 1.0 Public Identifier>
6A <Charset=UTF-8 (MIBEnum 106)>
00 <String table length>
45 <SI element start, with content 0x05 | 0x40>
C6 <indication element start, with content and attributes 0x06 | 0x40
| 0x80>
0C http://
03 (next is an ASCII string 00 terminated)
77 61 70 2E 74 61 69 2E 69 74 wap.tai.it
00
11 <si-id=>
03 (next is an ASCII string 00 terminated)
39 32 40 74 61 69 2E 69 74 [EMAIL PROTECTED]
00
08 <action=signal-high>
0A <created=>
C3 <OPAQUE data follows>
07 <Length field (7 bytes)>
19990625152315 1999-06-25 15:23:15
10 <si-expires=>
C3 <OPAQUE data follows>
04 <Length field (4 bytes), final 0s are omitted>
20030630 2003-06-30 00:00:00
01 <indication element attributes end>
03 (next is an ASCII string 00 terminated, the SI content)
56 75 6F 69 20 76 65 64 65 72 65 20 6C 65 20 4D 61 70 70 65 3F Vuoi
vedere le Mappe?
20 4F 70 7A 69 6F 6E 69 20 2D 20 53 63 61 72 69 63 61 Opzioni -
Scarica
00
01 <indication element end>
01 <SI element end>
