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

Post a Comment

Popular posts from this blog

How to logout from a login page in asp.net -

whenever click on logout button redirect me login page when im clicking on button redirect me last visited page. not using membership or windows authentication. session.abandon(); response.cache.setcacheability(httpcacheability.private); response.cache.setcacheability(httpcacheability.nocache); response.redirect("loginform.aspx"); if using session destroy session value on logout button click , can put check in app webpages if(session["sessionvaribale"].equals(null)) { response.redirect("logoutpage url"); }
Read more

Stack level too deep error after upgrade to rails 3.2 and ruby 1.9.3 -

i'm upgrading rails 3.0.9 app 3.2.13 , ruby 1.8.7 1.9.3. time try access controller action, following error started "/myapp/login" 127.0.0.1 @ 2013-07-25 07:10:06 -0600 systemstackerror (stack level deep): actionpack (3.2.13) lib/action_dispatch/middleware/reloader.rb:70 rendered /actionpack-3.2.13/lib/action_dispatch/middleware/templates/rescues/_trace.erb (1.5ms) rendered /actionpack-3.2.13/lib/action_dispatch/middleware/templates/rescues/_request_and_response.erb (5.2ms) rendered /actionpack-3.2.13/lib/action_dispatch/middleware/templates/rescues/diagnostics.erb within rescues/layout (22.6ms) the way i've been able page load without error clear out database sessions (rake db:sessions:clear) , restart rails server. allows 1 single request succeed , subsequent requests fail. i've tried comparing core config files working 3.2 app , have tried upgrade of gems. here's current gemfile: source 'http://rubygems.org' gem 'rails...
Read more