Well, it depends on your audience. But ideally, to support legacy browsers, you shouldn't assume they can handle a TIFF.
At the very least, load the TIFF, select the first frame (page), do a DrawImage into a new bitmap, save the bitmap as JPG to a memory stream, and send that to Response.
If you're not familiar with .NET's GDI+ image manipulation or that sounds hard, please see http://www.bobpowell.net/faqmain.htm for advice. Each one of these steps can be done with just a few lines of code. If you don't already know GDI+, it's worth learning for any web developer. That might make doing this 'the hard (but safe) way' worth it for the education alone. And if you already know how, it won't take but 1/2 hour.
If you must display multipage TIFFs, and you want the user to control which pages to see, you'll have to create a user interface to set the page number. If you're trying to display multiple TIFFs per page, that might get non-trivial, so consider displaying all the tiff #1 pages on the first web page, or, allowing them to view subsequent tiff pages by linking to another web page with prev/next tiff page buttons. It should be a generic page that accepts the filename and current page numbers (prev/next buttons would point to itself with +/- one page number) as URL parameters.
If you know you'll only be showing text documents instead of photographs, try sending single-frame GIFs instead of TIFFs to the browser for less Jpegginess on the text. But beforewarned - photos can look pretty bad a GIF.