Welcome to WebmasterWorld Guest from 220.127.116.11
The fact is that my visitors from that ISP (the biggest in my country) canīt access my site.
How can an ISP decide which sites to put inside such a proxy? How can we bypass it?
Iīm moving the domain to a new server, and removing the apache redirector. Will this solve it? Or will the domain continue to be blocked?
It's not clear why your site would be affected by a transparent proxy - they're supposed to be transparent, or invisible, to users.
As to why your ISP would do this, you'll have to ask them. I would expect that many or all sites they host would be similarly configured with respect to firewalls, gateways, routers, proxies, etc. They certainly would not put an individual site's server behind a proxy without charging you for it. And they would not do it to punish you, because it would be far less expensive to simply close your account.
Hopefully, moving your site to a new server and getting rid of the redirects and other complexities will improve things for you.
Some ISPīs are using transparent proxies to improve adsl speed. That was what happened to my .com domain . It cached some sort of error (I guess it didnīt handled properly the apache redirect), and that error (it seemed that he couldnīt find the page in itīs cache) kept appearing until it updated the cache. I removed the redirect, moved it to a new server, inserted an index (the same that itīs in .net domain), and now Iīm moving all files from the .net to the .com domain.
I have to be quick so that Google donīt think itīs duplicated content.
All is fine now. I was a bit in panic before I knew that it was a proxy problem.
NO proxy is supposed to cache any server error response, so this should be a one-time incident.
In order to limit damage in these cases, make sure you control what caches do with your pages if it is important to you. See Apache mod_expires and mod_headers. Make sure your custom error pages are non-cacheable!
# Default - Set http header to expire everything 2 weeks from last access, set must-revalidate
Header append Cache-Control: "must-revalidate"
# Prevent caching of error documents 403.html, 403x.html, 404.html, and 410.html
Header unset Cache-Control:
Header append Cache-Control: "no-cache, must-revalidate"
I'm aware that with header append, the header unset directive should not be needed... But it is, at least on my Apache 1.3.27 servers.
Replace the broken vertical "Ķ" pipes above with solid vertical pipes from your keyboard before attempting to use this code!
Many thanks for all your help. I think that the problem was that the isp didnīt handled correctly the 301 permanent redirect. I didnīt even had any personalized error page. Now that I removed the 301, and built a site on that domain (Iīm slowly moving all from .net to .com), everything is fine. Even so, Iīll add your suggestions to prevent that other errors happen. They are making some experiments with those new proxies, and sometimes things go wrong...