Vodacom GPRS proxy - stale data and forcing refresh?

[e11eveN]

I am developing a Symbian client that retrieves specific content (stock tickers, in this case) via HTTP. Currently, when connected via Vodacom GPRS i get stale data even after multiple requests:

- I've tried setting the 'Pragma:no-cache' and 'Cache-Control:no-cache' headers in my HTTP requests, to no avail. What proxy is Vodacom using? Is there specific headers i can use to enforce a refresh on it's part?

- The default 'Internet.GPRS' APN setup on a Nokia 6600 uses 196.6.128.12:8080 as the proxy. Creating a APN without setting a proxy solves the problem, but we would like to be able to use the default Vodacom settings.

Any pointers would be greatly appreciated?

 

[vodacom3g]

PM me your contact details and I'll put you in touch with the relevant internal guys who'd hopefully be able to help you.

 

[vodacom3g]

Also chat to Tazz_Tux. In a previous conversation with him (her?, it?), he came across as quite knowledgeable on HTTP headers.

 

[Tazz_Tux]

It???? geez !

Try adding the following to the headers:

Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache

If that doesn't work - add the following to the Cache-Control

Cache-Control: max-age=1

Laterz !!!

Also chat to Tazz_Tux. In a previous conversation with him (her?, it?), he came across as quite knowledgeable on HTTP headers.

 

[vodacom3g]

Well, sometimes I wonder if these Linux-types, and people that know HTTP headers off by heart, are from this planet...

 

[Clipse]

I still argue they come from Pluto.

 

[Tazz_Tux]

Damn this planet is hot !!!

I still argue they come from Pluto.

 

[e11eveN]

good morning

Thanks guys (girls?, bots?) - will give those a shot.

 

[Tazz_Tux]

Hey e11eveN,

Did this work?

Laterz !

Thanks guys (girls?, bots?) - will give those a shot.

 

[e11eveN]

Yes, it works beautifully, thanks. Have been playing with it over the weekend, and it's behaving itself nicely.

The proxy doesn't seem to care about the 'Pragma: no-cache' line, but the
'Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0' makes it fall in line like a good little soldier :/

I've thought about seeing which specific Cache-Control directive makes it happy and keeping my header down to that - but if it works, why fix it?

Either way - thanks for sharing your HTTP knowledge - much appreciated!

11

 

[alchamy]

Well, sometimes I wonder if these Linux-types, and people that know HTTP headers off by heart, are from this planet...

LOL