The Un-Official Proxomitron Forum

Hi

Sometimes my ISP redirects me to their home page when i request to any www domain and https (ssl) for an interval of hours every day. I´m still looking for an app to bypass this, but i found proxomitron very useful.

These are the headers reply i get from my isp's dns when i try to surf:

<html>
<meta http-equiv="Cache-Control" content="no-cache, max-age=0, must-revalidate, proxy-revalidate, s-maxage=0">
<meta http-equiv="Expires" content="now">
<meta http-equiv="Pragma" content="no-cache">
<meta http-equiv="Content-Type" content="text/html">
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
<meta http-equiv="refresh" content="0; url=http://www.xxx.myisp.com/xxxx/" />
<title>Redirection</title>
<meta name="robots" content="noindex,follow" />
</head>
<body>

</body>
</html>

I need to know if there´s a special filter to avoid or kill the "refresh" header, and how i may change meta and http headers. And maybe how to bypass a proxy cache if that´s the case.

Thnks.

switch to opendns servers and dont use your isp dns servers

personally, i BOYCOTT OpenDNS because of their overzealous nanny-state mentality!

they have TOO OFTEN flagged *good* sites as being "phishing sites"...
i rely on a more trustworthy HOSTS file instead...

although each and every time that OpenDNS *falsely* flags a site as a "phishing site", they DO "fix" the mistake and remove that flag - but it will take dang near a full WEEK, i don't see the "need" to have "good" sites UNAVAILABLE for that looooooong of a time due to overzealousness...

Here is a very basic filter to remove the meta refresh header:

Code:

[Patterns]

Name = "Kill ISP Redirect"

Active = TRUE

URL = "$TYPE(htm)"

Limit = 128

Match = "<meta http-equiv="refresh" content="0; url=http://www.xxx.myisp.com/xxxx/" />"

Of course, you'll need to update the URL (http://www.xxx.myisp.com/xxxx/) to the URL that they are actually using Smile!

Let me know how it goes!

Merged duplicate threads into this thread

I've also had caching issue in the past, which lead to some research....

What I found is that there is a rather strange header that exerts some control over caching, it's called Vary. By entirely eliminating that one, a goodly portion of my issues were resolved.

Code:

In = TRUE

Out = FALSE

Key = "Vary: blank it out [IN]}"

Match = "*"

I also deal with the Cache Control header, which is often used haphazardly by sites of less-than-stellar programming capabilities....

Code:

In = TRUE

Out = TRUE

Key = "Cache-Control: always cache public (in)"

Match = "*"

Replace = "public, max-age=3600, no-transform"

That forces everything to be public, which means that the browser can deal with it, the Expire timing is pretty generous, and that sites can't 'hide' behind transformed URLs - where it truly came from is what I see. Whistling

On non-Netscape browsers, I have found Pragma: no-cache effectively useless. That doesn't mean it should be ignored by one and all, that means only that I realize no benefit from it on my IE only system.

HTH

Oddysey

hmm, the no-transform is very interesting indeed...
is this just an Opera turbo (poc) thing that those of us using ie-shells don't really need to worry about?

(Jul. 06, 2011 12:57 AM)ProxRocks Wrote: [ -> ]hmm, the no-transform is very interesting indeed...
is this just an Opera turbo (poc) thing that those of us using ie-shells don't really need to worry about?

My guess would be 'No', it's probably useful to many/most browsers (and their attendant plug-ins). But notice the word "probably" - I'm no expert! I can say that for IE6.1, a lot of my issues were suddenly short-circuited by using this directive.

I guess experimentation is all I can offer. I'm sure that not everyone will benefit, but at the same time, it's there for a reason. Why not kill a few moments and see what happens? Smile!

Oddysey

steellar

susa

ProxRocks

Kye-U

Oddysey

ProxRocks

Oddysey