redirect or render

[ebound]

I run an original content news site. On the front page I list recent headlines with a small description of each article. Each of these links to it's story.

I have recently implemented a membership system. Once this system is stable I want to be able to put some of the stories listed on the home page behind this login. The idea is to allow users that aren't logged in to click on the headline and be taken to the page where they will be asked to login or instructed to signup.

The questions here are:

Do I redirect the user to a page dedicated to signing up? Home Page -> NewsPage.asp (redirect) -> LoginSignup.asp
If this is the case, what status code do I give on the redirect page?

or

Do I render the signup information on the page where the story resides? Home Page -> NewsPage.asp (contains login/signup instructions)
If so is there a html status code for a page that requires a subscription?

Make sense?

[Fotiman]

I would probably redirect, passing in the referring page URL so that you can redirect them back after processing the login. Assuming you're using ASP, you can use the Response.Redirect method.

[edited by: Fotiman at 5:17 pm (utc) on Oct. 23, 2007]