ad.doubleclick.net blocks IE's Back button

  • Thread starter Thread starter _dee
  • Start date Start date
NB: I just hear, that shutting off the "friendly http errors" in internet
options, advanced (which one should do, anyway) is supposed to stop that
security warning. I don't know if it also stops the pollution of the
history button. But worth a try for anyone before trying Homer ;-)

Kai
 
I see both the security warning AND the history pollution with friendly
errors turned off (which is how I usually leave it set).


Rob
 
NB: I just hear, that shutting off the "friendly http errors" in internet
options, advanced (which one should do, anyway) is supposed to stop that
security warning. I don't know if it also stops the pollution of the
history button. But worth a try for anyone before trying Homer ;-)

Kai
Click to expand...

I hope I'm not speaking too soon, but it appears that disabling
'friendly http errors' stops the 'ads' URL from appearing in the back
button. No idea why.
 
As you can see in my reply, that didn't work for me, so maybe there's
something else at play as well here.


Rob
 
As you can see in my reply, that didn't work for me, so maybe there's
something else at play as well here.
Click to expand...

Well, this is officially bizarre then. Rob, I have
Tools->Privacy->Advanced first party and third party cookies set to
block. I unblock specific sites as needed. (Session cookies are
enabled)

I changed "Friendly HTTP Errors" as suggested by Kai, and the Pain in
the Back Button (ad.doubleclick) seems to have vanished. Can it be
that easy? I'm not sure what purpose the 'Friendly Errors' have then,
or how that would be connected.

If you can send a URL that turns up problems for you, I'll give it a
try to see if it happens here. If not, maybe we can compare other
settings. I'm running IE 6 though. Not sure I want to step into IE7
yet from what I've heard.
 
_dee schrieb am Sat, 10 Mar 2007 04:19:03 -0500:
I changed "Friendly HTTP Errors" as suggested by Kai, and the Pain in
the Back Button (ad.doubleclick) seems to have vanished. Can it be
that easy?  I'm not sure what purpose the 'Friendly Errors' have then,
or how that would be connected.
Click to expand...

You block these sites successfully, so IE generates a friendly error page
and displays it in the area the iframe occupies. You should see it there,
as Robert did. And that friendly error page is then pushed in the history.
For reasons unknown, I don't see how that makes sense. But that's how it
is.
If you shut friendly error pages off IE will display the error from the
server. And since you don't have a server there it gets no response. In
that situation IE would normally drop back to friendly error pages and
display one. Apparently it doesn't and so the problem is fixed for you.

Kai
 
_dee schrieb am Sat, 10 Mar 2007 04:19:03 -0500:


You block these sites successfully, so IE generates a friendly error page
and displays it in the area the iframe occupies. You should see it there,
as Robert did. And that friendly error page is then pushed in the history.
For reasons unknown, I don't see how that makes sense. But that's how it
is.
If you shut friendly error pages off IE will display the error from the
server. And since you don't have a server there it gets no response. In
that situation IE would normally drop back to friendly error pages and
display one. Apparently it doesn't and so the problem is fixed for you.
Click to expand...

Yeah, baby! Pretty involved, so I'll have to check into that a bit
further. Thanks, Kai! I never would have looked at the 'friendly
errors' switch.
 
_dee schrieb am Sun, 11 Mar 2007 03:07:51 -0500:
 I never would have looked at the 'friendly
errors' switch.
Click to expand...

Well, it was just coincidence that another MVP mentioned it to me with a
similar, but not connected problem.
It's obviously what you can try first and what everyone should do, anyway,
so you can see the real error pages if there is one. And if it doesn't
work there's hosts and Hostsexpress and Homer, as explained by Robert.

Kai
 
Back
Top