Re: cflocation vs. server side redirect.

2002-09-09 Thread Joee Bastian
CFMX Server side redirect... cfscript GetPageContext().forward(Somepage.cfm?myid=7); // works similar to asp3.0 server.redirect(whatever.asp) /cfscript Yes.. the server redirects/passes/controls the flow of the application. Cookies should work fine. Some of the new CFMX books advise this

RE: cflocation vs. server side redirect.

2002-09-09 Thread Bryan Love
server side redirects allow the use of cookies since the page is processed by the browser. Cflocations are faster since the relocation happens at the server and does not have to go to the browser and back again (which is why cookies don't work with cflocation by the way). There are many

RE: cflocation vs. server side redirect.

2002-09-09 Thread Bryan Love
vs. server side redirect. server side redirects allow the use of cookies since the page is processed by the browser. Cflocations are faster since the relocation happens at the server and does not have to go to the browser and back again (which is why cookies don't work with cflocation by the way

RE: cflocation vs. server side redirect.

2002-09-09 Thread Tony Weeg
: Joee Bastian [mailto:[EMAIL PROTECTED]] Sent: Monday, September 09, 2002 3:04 PM To: CF-Talk Subject: Re: cflocation vs. server side redirect. CFMX Server side redirect... cfscript GetPageContext().forward(Somepage.cfm?myid=7); // works similar to asp3.0 server.redirect(whatever.asp) /cfscript Yes

RE: cflocation vs. server side redirect.

2002-09-09 Thread Dave Watts
cfscript GetPageContext().forward(Somepage.cfm?myid=7); // works similar to asp3.0 server.redirect(whatever.asp) /cfscript so does this bit about works similar need to be there? I havent the faintest idea what was right or wrong in asp3.0 and have seen this same snippet

Re: cflocation vs. server side redirect.

2002-09-09 Thread Jochem van Dieten
Bryan Love wrote: server side redirects allow the use of cookies since the page is processed by the browser. Cflocations are faster since the relocation happens at the server and does not have to go to the browser and back again (which is why cookies don't work with cflocation by the way).

RE: cflocation vs. server side redirect.

2002-09-09 Thread Dave Watts
server side redirects allow the use of cookies since the page is processed by the browser. Cflocations are faster since the relocation happens at the server and does not have to go to the browser and back again (which is why cookies don't work with cflocation by the way). This is

RE: cflocation vs. server side redirect.

2002-09-09 Thread Ken Brocx
Subject: RE: cflocation vs. server side redirect. cfscript GetPageContext().forward(Somepage.cfm?myid=7); // works similar to asp3.0 server.redirect(whatever.asp) /cfscript so does this bit about works similar need to be there? I havent the faintest idea what was right or wrong in asp3.0

RE: cflocation vs. server side redirect.

2002-09-09 Thread Bryan Love
-Original Message- From: Jochem van Dieten [mailto:[EMAIL PROTECTED]] Sent: Monday, September 09, 2002 12:25 PM To: CF-Talk Subject: Re: cflocation vs. server side redirect. Bryan Love wrote: server side redirects allow the use of cookies since the page is processed by the browser

RE: cflocation vs. server side redirect.

2002-09-09 Thread Tony Weeg
-Original Message- From: Ken Brocx [mailto:[EMAIL PROTECTED]] Sent: Monday, September 09, 2002 3:34 PM To: CF-Talk Subject: RE: cflocation vs. server side redirect. No tony, The part // works similar to Does not have to be there. It's commented piece of code. Anything after

RE: cflocation vs. server side redirect.

2002-09-09 Thread Dave Watts
This is incorrect. cflocation simply sends a HTTP 302 Found statuscode to the browser together with a Location header. How could the URL one sees in the browser possibly change if nothing was send to the browser? This is my understanding: Of course something is sent to the

Re: cflocation vs. server side redirect.

2002-09-09 Thread Joe Eugene
//single line/* multi line or blocks of code) Joe - Original Message - From: Ken Brocx [EMAIL PROTECTED] To: CF-Talk [EMAIL PROTECTED] Sent: Monday, September 09, 2002 3:34 PM Subject: RE: cflocation vs. server side redirect. No tony, The part // works similar to Does not have

Re: cflocation vs. server side redirect.

2002-09-09 Thread Jochem van Dieten
Bryan Love wrote: This is my understanding: Of course something is sent to the browser, but AFTER the cflocation happens. Say for example you have page1, page2, and page3. Page1 is a form, page2 processes the form, and page3 is a thank you page. Server side (cflocation): - user

Re: cflocation vs. server side redirect.

2002-09-09 Thread Jochem van Dieten
Dave Watts wrote: When you use the CFLOCATION tag, the server sends back a Location header. The browser doesn't display the page which contains the Location header, but it does receive it. It then requests the URL specified in the Location header. So, using your step-by-step approach,

RE: cflocation vs. server side redirect.

2002-09-09 Thread Dave Watts
Indeed easy. But wrong :) Although your description of what happens is quite accurate for the current browsers, you are depending on features that are not compliant with the HTTP/1.1 specification. ... A redirected POST should result in a POST for the next page, not a GET, and a