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 submits page1
> - server processes page2
> - server requests page3
> - server processes page3
> - server returns page3
>
> Client side (using JS or HTML):
> - user submits page1
> - server processes page 2
> - server returns page2
> - browser requests page3
> - server processes page3
> - server returns page3
<quote>
10.3 Redirection 3xx
This class of status code indicates that further action needs to be
taken by the user agent in order to fulfill the request. The action
required MAY be carried out by the user agent without interaction
with the user if and only if the method used in the second request is
GET or HEAD. A client SHOULD detect infinite redirection loops, since
such loops generate network traffic for each redirection.
[..]
10.3.3 302 Found
The requested resource resides temporarily under a different URI.
Since the redirection might be altered on occasion, the client SHOULD
continue to use the Request-URI for future requests. This response
is only cacheable if indicated by a Cache-Control or Expires header
field.
The temporary URI SHOULD be given by the Location field in the
response. Unless the request method was HEAD, the entity of the
response SHOULD contain a short hypertext note with a hyperlink to
the new URI(s).
</quote> RFC 2616 HTTP/1.1
IMNSHO RFC 2616 is one of the very few RFC's, possibly the only RFC,
every CF developer be familiar with.
Jochem
______________________________________________________________________
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
