chrometweaks.org

Any iPage web hosting allow bulk email. please help?

Click Here To View All Answers...


First of all Any iPage web hosting allow bulk email. please help? Thanks for any response. Another quick question... First off, I apologize if this is the wrong forum. Since this is a meta tage issue, I figured maybe I should have put it with the "Search Engine" forum, but it's not actually a search engine thang..

What i've got is a.

Site.

With a lot of pages that are updated constantly. But people are always seeing stuff that's a week old..

I've been using.

<META HTTP-EQUIV="no-cache" content="no-cache">.

To get browsers to stop displaying old news, but it's not working. Any suggestions? I don't want to use an expiration date, because this can cause spiders to dump your page from it's search results. i've seen something before that was "revisit after" or something like that. What's that doing, and does it work any better? Should I use a combination of meta tags, and if so, which ones?.

Thanks.....

Comments (9)

I would like to know the answer too. Anyone here know what is the answer to your question. I'll do some research in Google and get back to you if I bump into an answer. You should email the people at iPage as they probably could assist you..

Comment #1

Okay, but isn't that what the meta no-cache is for? to tell the browser to pull up the online version no matter what?..

Comment #2

Actually I think you need to use a pragma directive to change the behavior of the food chain, I believe the correct no-cache tag is this:.

<META HTTP-EQUIV="Pragma" CONTENT="no-cache">.

I'm not sure it works on all systems though, there might be some server side dependency since it's effecting the request/response chain. Give it a try and see what happens..

Kevin..

Comment #3

Hi, all..

<META HTTP-EQUIV="Pragma" CONTENT="no-cache">.

This prevents caching on local machine.

ONLY.

When it is viewed over a.

SECURE.

Connection (https). When this tag is used over a non-secure connection, the browser.

WILL.

Cache the page and mark it to be immediately expired..

If you have ASP, you can also use this:.

<% Response.CacheControl = "no-cache" %>.

<% Response.AddHeader "Pragma", "no-cache" %>.

<% Response.Expires = -1 %>..

Comment #4

So (bear with me; i'm a moron) if I use.

<META HTTP-EQUIV="Pragma" CONTENT="no-cache">.

On a non-secure web page, then people will see a non-cached version.

Daily.

? Or just whenever the browser is set to check for an updated version?.

Thanks tremendously, whkoh!..

Comment #5

On a non-secure site, <META HTTP-EQUIV="Pragma" CONTENT="no-cache"> will force the page to expire, hence causing the browser to refresh...

Comment #6

I think the HTTPS problem was actually being called a bug. I seem to remember that from reading about pragma directives a while back..

You will just have to give it a try transmothra, I'm not really sure how well integrated the pragma directives are into browsers and servers, and may vary from browser to broswer. Really old browsers will not support pragma directives at all but unless you really needed 100% compliance that shouldn't be a problem..

Kevin..

Comment #7

I heard that f2s.com servers have a caching problem...

Comment #8

You start with META tags in the HEAD of the page..

Not well supported by some browsers..

The first instructs no caching:.

<meta HTTP-EQUIV="Pragma" CONTENT="no-cache">.

The second is necessary because IE5 ignores the pragma:.

<META HTTP-EQUIV="Expires" CONTENT="-1">.

That expires the page as soon as it is born..

However that may still not work in IE because it it is in the head where.

It has to be. In some kind of twisted logic IE sees the META tags, but.

Because the page has not yet been loaded there is nothing to cache so it.

Ignores it. Then when the page is loaded, it caches it. The solution.

From Micro$oft is to duplicate the tags after the end of the body..

However they have to be in the head so you end up with this silly looking,.

But effective page setup:.

<HTML>.

<HEAD>.

<TITLE></TITLE>.

<META HTTP-EQUIV="Pragma" CONTENT="no-cache">.

<META HTTP-EQUIV="Expires" CONTENT="-1">.

All the other head stuff.

</HEAD>.

<BODY>.

All the good stuff that makes the page worthwhile.

</BODY>.

<HEAD>.

<META HTTP-EQUIV="Pragma" CONTENT="no-cache">.

<META HTTP-EQUIV="Expires" CONTENT="-1">.

</HEAD>.

</HTML>.

For ASP if you want the same non-cache effect, here's the header.

Information:.

<% Response.CacheControl = "no-cache" %>>.

<% Response.AddHeader "Pragma", "no-cache" %>.

<% Response.Expires = -1 %>.

I don't know if once does it for ASP or if you have to repeat.

That as well..

And of course Netscrap always has to add a twist of it's own. Pages.

With forms in Netscrap can be a problem especially for secure environments..

Netscape suggests the following JavaScript be used in the BODY tag.

Of all pages that should not be cached:.

<body onLoad="if ('Navigator' == navigator.appName) document.forms[0].reset();".

With all of that there is still a small chance that there is still an.

Unreported bug or a fringe browser that will screw up but this should.

Be 99% effective..

Using -1 as an expiry will cause most robots to ignore the tag..

Cd&..

Comment #9

And it is so confusing!.

But I can live with that.

They have their own web caching servers...

Comment #10


This question was taken from a support group/message board and re-posted here so others can learn from it.