Verizon DSL as interconnectivity ISP: How to get around their caching web pages
Posted on 2006-10-30
As a web designer, i have about a half dozen clients who use Verizon DSL to connect to the web.
One of my workflow techniques is to design in real time on the phone with the client, uploading edits and they Refresh/Reload to see the updates. (and even aside from this "interactive/instant" design process, i have one client that wants to guarantee that other people in the world with Verizon will see his latest content [a valid point, altho low probability that someone else in that leg of the Verizon network would view the old cached copy])
Unfortunately, consistently for the past several years since i started working with clients who have Verizon, Verizon caches the web content and i have to have them change the URL in order to see the updated results. (URL change means using one of several techniques to fool Verizon not to use the cached page: "incrementing" the filename, or changing the domain, using the apache ~user syntax to fool verizon (at my servers apache resolves back to the intended file to be served up)). In addition i'd rather not change the TTL for the DNS.
Verizon is the only connectivity ISP that i have this problem with, amongst the many ISPs that my clients use across the country.
Verizon refuses to talk with me since i'm not their client, and i think it's tacky to do a con call to take up my client's time to wait to speak with a tech support person who probably will deny the situation, etc.
So, my question is: does anyone have an alternate workaround?
(I'm also considering using a tool like VNC to let the client see my live screen; however, i have one client who is incredibly difficult to deal with and blames the Refresh/Relad on me and doesn't want to deal with anything other than his web browser)