parameterized URLs necessary for output-caching ?

[John A Grandy]

For a highly scalable app, to properly implement output-caching of pages
(page-fragments, user-controls, etc.) is it necessary to utilize
parameterized URLs ?

Is there an alternate method to implement output-caching ?

The reason I ask is that I don't like parameterized URLs because it is a
complex and time-consuming process to threat model and write code to protect
against query string hacks.

I'd like to ask this question for ASP.NET 1.1 ...... and ASP.NET 2.0
.........

My app uses ASP.NET Web Controls for all user-entries.

Thanks.