A blog about me, my doings and everything I think deserves attention.

Caching on part 2

So, I wrote about how caches everything and it is ridiculously annoying to debug something that is live (basically when you need it the most), right? Yeah, here’s a chat log with some of their support people from a while ago, I’ve completely dropped them and will move my last remaining domain from them when it runs out.

Welcome to the chat support. We are doing our best to answer your queries soon. We kindly ask for your understanding that our answers may be delayed during busy periods.
You are now chatting with ‘Grace
Grace: Thank you for using 24/7 Interactive Online Support. My name is Grace. How may I assist you?
you: Hey, I have a question about a domain
you: is any kind of .htaccess caching active on domain X or domain Y?
Grace: Hello
you: I remember telling you guys to turn it off
Grace: Please hold on while I check.
Grace: php cache is already disable for both domains. But the server cache is still active since this are not allowed to be disabled. As a workaround, you may have to upload an entirely new file to your webspace to reset the caching or just wait for few minutes delay on the caching for the changes to update.
you: disable it.
you: the customer did not sign up for this
Grace: Sorry but we cannot disable the server cache. Its not possible
you: Sorry, that is a lie, please make your superior call me. My phone number is 0045 xxxxxx
Grace: Unfortunately, we dont have phone support here
you: unfortunately you’ll have to find someone with a phone then
you: don’t give me info about having no phone, I’ll take this case as high as I need to
Grace: I will transfer you to a superior to explain this better
Please wait while I transfer the chat to ‘Eduard‘.
You are now chatting with ‘Eduard
Eduard: Hi there
Eduard: what seems to be the issue?
you: hello
Eduard: hi there
you: Grace misinformed me about that disabling server caching is not possible.
you: It is possible and I want it disabled for several domains. Being a web dev on your platform is unacceptable
Eduard: are you referring to varniche cache? or php cache?
you: the varniche, responsible for files
you: the php cache I told you guys to disable long ago
Eduard: yes which is disabled
Eduard: so which cache are you referring to disable?
you: the file cache
you: especially for me testing on .htaccess
you: what’s the activity time span anyways?
Eduard: ok let me check on that
Eduard: I got info that you can add this line in your .htaccess to disable file cache
Eduard: header add “disablevcache” “true”
Eduard: then it will be disabled
you: just on top of the file?
Eduard: yes please
you: okay, didn’t work for me
you: www.DOMAIN should point to http://DOMAIN
Eduard: you have to wait for 30-60mins for that
Eduard: give it time please
you: alright, when can I expect this caching to be disabled by default?
Eduard: no its not by default
Eduard: its enabled by default
you: alright, when can I expect it to be disabled by default?
Eduard: we have no plans on that
you: When can I expect you to start planning on that?
Eduard: that I do not know sorry you can send email to for such inquiries
you: Nah, I think I’ll just blog about it again, gives me a lot of hits icon smile Caching on part 2
you: oh and of course move all my domains
Eduard: oh ok then
Eduard: Is there anything else I can assist you with ?
you: You’d not consider sabotaging your own company, would you?
Eduard: sorry I do not understand what you mean
you: Oh, nothing big, just leak some documents or embarass your superiors?
Eduard: sorry but no
you: Okay, anything else you maybe could think of?
Eduard: no sorry
you: Hmm, that’s not very creative.
you: Alright, if you come to think of something, you can always send me a mail in these matters.

16 comments already

16 Responses to “Caching on part 2”

  1. Lennart says:

    hi, wo bist du denn hingewechselt?

  2. Lennart says:

    ah stimmt, hatte das mit dem Server vergessen.
    Hast du was hardening und so angeht spezielle Dinge gemacht?

  3. Adam says:

    Admittedly the situation might have changed since June, but:

    I just had a similar experience – I went on live-chat, asked them to disable the file cache – and they did.

    The difference in my approach? I was polite, and asked nicely! Try it, it’s good for the soul, and for productivity! :)

  4. Jens Henrik says:

    It´s your MySQL Table overhead. Optimize your tables “Overhead” if it exceeds 1kB.

    Det hjalp hos mig, jeg har pryglet og slÃ¥et oven i hovedet. De useriøse nødder…

    • Haha, det var nok en sjov unskyldning :D

      • Jens Henrik says:

        Det var sgu ikke de idioter, der fandt ud af det, men mig selv.
        Jeg kærer både phpbb og WordPress på forskellige domæner hos dem.

        Du kan ikke lmgås Varnish Cache Server hos dem, da den allerede er slået fra.
        Hvis du får en 503 error, er det en default meddelelse fra php.
        Time outber 35 sek, hvorefter php fortsætter 15 sek endnu, men aldrig komemer videre…
        Her har de ikke engang fundet ud af, hvordan det omgås, selvom det er simpelt.

        Det var blot for at give dig løsningen på dit problem. Pøj, pøj!

        • NÃ¥, jeg troede det var dem der bare var useriøs i supporten. Du kan godt fÃ¥ php cachen slÃ¥et fra, men ikke den til statiske filer, som er lidt en skam nÃ¥r mal lige vil patche et stylesheet eller en .htaccess fil.

  5. Oliver says:

    Det handler virkelig om tale pænt til dem. JEg har forespurgt mange gange pÃ¥ netop dette dødirreterende emne og fælles er deres “please allow 30 minutes..” men udfaldet kan gÃ¥ begge veje derefter. Efter 30 min. kaffepause er man ret dizzy og kommer til at være spydig som det ses her.

    fedt artikel-emne i og med at så mange små kunder ligger hos dem.

  6. JOey says:

    I think is aware of the developers getting f*cked with these cache settings. I’ve used the 24/7 chat and asked for a cache disable on their side, problem fixed in 10 seconds!

  7. Simon says:

    Ich hab das gleiche Desaster hier, jedes Mal wenn ich was an meiner Page machen will klappt es nicht, dann wieder mal ein paar mal, dann wieder nicht… Ich hatte ungefähr den gleichen Chat-Austausch wie du. Nebenbei erscheint im Webmail-Client mittlerweile täglich “Internal Server Error” für mehrere Stunden. Für einen der sein Geld damit verdient einfach inakzeptabel. Naja, will mich nicht beschweren, denn bei All-Inkl bin ich schon lange mit anderen Projekten, wollte damals nur ausprobieren. Warum meine eigene Seite nicht auch da liegt…. weiß ich auch nicht ;) Für so wenig Geld bekommt man eben keinen guten Support. Providerwechsel steht an….;)

    Ich hab mal zu All-Inkl. geschrieben vor längerem, falls es jemand brauchen kann:

  8. Fastone says:


    I’m on the support with about this issue now, for the 10th time!…

    It’s annoying, and as a webdesigner, I can’t work like this! I have also told them to turn this off for my sites, and I don’t get a no on that. But it may seem like it is switched back on again.

    I have lead all my web clients to the last years, because of the price, stability, support and just that it works perfectly for most clients needing only one DB.

    No I think I have to switch. Any suggestions here? …

    The sweet girl on support is still trying to help me. I just added a code in my header.php file 30 min ago, and I still cant find it in my source code! …


  9. Jeff says:

    Contacted support about the issue via live chat… They said no problem, they will disable server side caching and I should see the changes instantly after my server restarts. (eta: 20 min)

    Had a few bumps but support has been pretty good about getting them ironed out.

    Lets see if they keep it up.

  10. KrisBerg says: are nice people, period. They have 24/7 chat support for you customers that pay f**king nothing for a web server. I got at least 10 web sites for clients on these servers, and every time I sign up, I ask them to turn off PHP-caching, and the .htaccess line to disable Varnish is self handled… It’s done in a few seconds.

    Give these people a break – they’re here to help you!

  11. dirdi says: published a document[0] about the varnish cache and how to disable it, finally. Adding ‘header add “disablevcache” “true”’ to .htaccess – like also suggested by Eduard – works for me. After that, you have to wait nonrecurring ~10min until the change takes effect.


Leave a Reply