design - Is the use of CFLOCATION good/bad practice for "next step" operations? -


i design step-by-step processes (i.e. shopping cart) in following way:

  1. form posts itself
  2. on post, validate entries.
  3. if not valid, display form error messages.
  4. if valid, save entries (to session or database, etc.), send user next step/page using <cflocation />.

my question is, proper use of <cflocation />? looking @ definition tag, seems should used actual "moved files", considering sends http header response code default, , allows enter another, if needed.

in case, there's no "moved files", want send user page after they've completed task. if @ iis logs, misleading, seeing bunch of 301s.

i'm looking best practice principle here, assuming cannot re-engineer whole process use ajax.

seems fine me. cflocation 302 redirect default, it's fine temporary redirects. unless you're specifying 301 statuscode?


Comments

Popular posts from this blog

curl - PHP fsockopen help required -

HTTP/1.0 407 Proxy Authentication Required PHP -

c# - Resource not found error -