|
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.
|
Title: Messaggio
- Re: R: Setting No Cache in WAP Push Claudio Montanari
- Re: R: Setting No Cache in WAP Push Aarno Syv�nen
- R: R: Setting No Cache in WAP Push Claudio Montanari
- Re: R: R: Setting No Cache in WAP Push Aarno Syv�nen
- R: R: R: Setting No Cache in WAP Push Claudio Montanari
