You should also use the HTTP 1.1 cache-control: no-cache, e.g.
Bear in mind that not all browsers will honour meta http-equiv directives. So, ideally, you should use the HTTP cache-control and pragma directives directly at the HTTP level. Most server-side processing systems (JSP, ASP, etc.) should let you get at these.
<META HTTP-EQUIV="Cache-Control" CONTENT="no-cache">
See http://www.w3.org/Protocols/rfc2616/...4.html#sec14.9 and http://www.w3.org/Protocols/rfc2616/....html#sec14.32 for details.
There's a whole raft of other caveats, too.
Remember that using these directives can break the user's back button, which WILL cause severe usability problems.
Preventing all caching in a long sequence of forms (e.g. an e-commerce system) will probably cost you a very large number of broken sessions, as users find out the hard way about the back button being broken. This is a really good way to annoy users and lose business. As such, you should only do this if you have a REALLY good reason to do so. "My session handler can't cope with users using their back button" is NOT a good enough reason, IMO.
The usability implications are the main reason for the existence of the more flexible Cache-Control directives in HTTP 1.1. Unfortunately, support for HTTP 1.1 is lacking in many older browsers.