I was reading an article some few seconds back, it was talking about browser caching,
being a cause of problem for clients not seeing the latest version of your web page.

Now, my question is that, can someone supply us with some techniques for forcing
the browser to always reload the following types of files:
javascript, images, css

This is an open question realy, because there are so many methods to do this. . .
there are both client and server sides methods.

When using ajax too, the same problem occurs atimes. . .

I think you guys should read this article, http://www.vodahost.com/vodatalk/bluevoda-tips-tricks-shortcuts/15573-browser-caching.html
The method highlited here is not one of the methods i use at all, the one i use too is about is effective as this, but my favorite method
is universal for any media that will be served over the web, it includes even music and videos.

I don't know if "bypass cache" is the right phrase here, IMHO. I would rather say, "how to force the latest version of a file" or "how not to load a cached file". I know, tis a play on words but I think mine is clearer

What I am used to seeing is tacking on a version variable to the end of files like CSS and JS. So for example, if I have a file called yawa.css, if I want to guarantee that I always am pulling the latest version from the server, I can do something like so:
www.xyz.com/css/yawa.css?v=1.

The "1" above is a random number generated by backend code (PHP, JSP, etc). When I new version of the file goes out, all we would do is update the version number.

For those who can afford (usually corporations), they use a company called akamai. You send your files to them, they host it for you and handle all the caching issues for you.

You are free to remodify the phrase as you please, at least i have provided a thread that examplify what i was trying to say sha. . .
oya, answers now, BTW yawa, your message was swallowed by the stooopid bot, but as always, we know how to decode it. . .

Let me try again. ye ye spam bot

You tack on a name value pair at the end of the file name, something like version equals 1.1. Then each time you update the file, you update the version number. The version number would typically be assigned via a backend language.

On a corporate scale, companies tend to use the services of akamai, who host your files and handle all the caching issues for you.

Can we see some sample codes por favor, as a programmer, i can only read codes, i cannot read simple ingles fairly easily. . . (because i have dual core processors in place of brain cells)

yawa-ti-de:

www.abc.com/css/yawatide.css?version=1.4.3

tres bien, there is another code that allows you to use the same name for all your files, it
just clears the cache using php cache code. . .which seem to have skipped my memory at
the moment, it can be used to deliver any content type.
I will do a dns lookup on some sites i have used that technique on, i know it was used in
that my code http://.net/demos/jupload/
the url of the image is constantly http://.net/demos/jupload/demo.php
but immediately any new photo is loaded, it overrites the old one. . .and the changes
reflect almost immediately without changing the url

Versioning as yawa-ti-de mentioned.

Ajax posts are not cached, so sending a post request instead of get shouldn't do any caching.