Telkom Caching

Y

youradsl

Well-Known Member
Joined
Jan 5, 2006
Messages
150
Reaction score
0
Can anyone tell me what to do about this damn caching by Telkom (I think that's the problem). Im working on a website and moved my Nameservers to a new host, it already propogated through the inteernet but the old site is still showing up. This only happen when I connect with my Telkom connection (running through a proxy or using IS works fine - the new site shows up).

I have cleared my temp internet files, hit Ctrl+R and Ctrl+F5 about a thousand times but nothing. Any ideas???
 
I too am interested in finding an answer to this. I believe the "expires" HTML property of the page controls this to a degree, but obviously it is too late to set this once the server has cached the page!

I had similar issues with a "GPRS test page". This page remained set when connecting to it via my cell phone, even when the page no longer existed. P1ssed the hell out of me.

It may also be that any script on the page forces the cache to be overwritten, as the "real" server needs to be involved then. So, adding <?php> <?> to the page may sort this out - not sure, so advice would be appreciated here :)
 
i've had a similar problem in the past. i phoned telkom and told them their transparent proxying (squid) was caching my page even though the correct heers were sent and the correct html meta tags were set.

the guy on the phone told me to remove the proxy settings from my browser (which didn't exist). he stood firmly on his point that they do not cache http traffic. he didn't even know what a anonymous proxy was. i gave him my url and the proxies ip address and asked him to escalate the matter to 2nd level support.

a few hours later the problem was solved; never heard from him again.
 
To fix it from your end add the following to the static DNS <hosts.> file:

[Webserver IP address] [FQDN eg www.mydomain.co.za]

This is also a clever way of accessing your domain before the DNS entry has propagated on the internet.
 
What about adding
<META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE"> ?
 
James said:
What about adding
<META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE"> ?
Click to expand...

Does not always work - I almost lost a client due to Telkom's mismanagement of their proxies (moved the client to M-Web dial-up and all worked fine)

Just as Telkom sets its own rules in general, they also set non-standard rules on their proxies.

Why should they conform to decent rules? They are a law in themselves!
 
myadsl said:
Can anyone tell me what to do about this damn caching by Telkom (I think that's the problem). Im working on a website and moved my Nameservers to a new host, it already propogated through the inteernet but the old site is still showing up. This only happen when I connect with my Telkom connection (running through a proxy or using IS works fine - the new site shows up).

I have cleared my temp internet files, hit Ctrl+R and Ctrl+F5 about a thousand times but nothing. Any ideas???
Click to expand...
You can try and add something to the parameters on the web page.

eg http://my.web.site/?test

This might make Telkom reload the site.

Cheers

Dean
 
andres101 said:
he stood firmly on his point that they do not cache http traffic.
Click to expand...

Typcial. I seem to recall their (Telkoms) reasons for charging more for UNshaped ADSL was because they could not use proxies to limit international bandwidth - now they do not even have a proxy. Typical.
 
bekdik said:
telkom always have 3 sides to a 2 sided argument ...
Click to expand...

Yeah, get two of their spin doctors in to an argument - with neither of them knowing the other works for Telkom, and imagine the interesting scenarios that would come up.
 
Mweb had the same annoying problem. The worst was if I changed the home page suffix - eg from www.abc.com/index.htm to www.abc.com/index.html the cache would keep going to the first one if you just entered www.abc.com - everyone outside the network saw the changed before I did!

So, either put the full page address ie - www.abc.com/index.html or better still www.abc.com/index.html? The '?' will force it to bypass the cache.

Also add the meta tag as suggested above to all your html pages.

Keep in mind like my mweb problem - chances are everyone outside of telkom is seeing the new stuff.
 
Thx guys.

Does anyone knows if their's a time limit on this caching crap before they reload your page, or could it go on for weeks.

I'm currently running through a proxy - so it works ok - but don’t want to do it forever.

Not even the “?” at the end work - it's still showing the damn old page on the old hosts web.

Are these people mad caching in such a way - the damn website is on a different server, with a different host and a different homepage – but still nothing.

James said:
What about adding
<META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE"> ?
Click to expand...
Thx – something like this might help, but only once the problem is fixed already, as it is still seeing the old hosts welcome page as my main page.

It is so bad. Even if I try to connect with my ftp client without using the proxy - it says that it can’t connect - switch to proxy and all work fine.
 
andres101 said:
i phoned telkom and told them their transparent proxying (squid) was caching my page even though the correct heers were sent and the correct html meta tags were set.
Click to expand...

Don't they use a Netcache box ???.
 
I also had frustrations with the "sticky" cache. One way of temporarily solving this is entering yourdomain.com without the "www" if your webservice caters for this (all of Hetzner's domains work like that). This will pull the new pages through 'cause the cache sees it as a different domain. Then you are back to step 1 of course and you have one last chance, use your domain's IP address 197.7.147.165 in the browser. Brilliant thread, i've got this one marked to learn more about beating the beast!
 
DearHeart said:
I also had frustrations with the "sticky" cache. One way of temporarily solving this is entering yourdomain.com without the "www" if your webservice caters for this (all of Hetzner's domains work like that). This will pull the new pages through 'cause the cache sees it as a different domain. Then you are back to step 1 of course and you have one last chance, use your domain's IP address 197.7.147.165 in the browser. Brilliant thread, i've got this one marked to learn more about beating the beast!
Click to expand...
Thx for all the help guys. I should have known to try without the www - thx it worked. Funny enough I tried the IP address first and even that did'nt work.
All seems to be sorted - for now anyway.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X