Here's the HTTP headers for a simple cflocation example. I've got two pages page1.cfm and page2.cfm. page1.cfm hasa <cflocation url="page2.cfm"> to page2.
1. Client requests http://mark.gruden.int/workspace/Tests/CF/page1.cfm ---------------------------------------------------------- GET /workspace/Tests/CF/page1.cfm HTTP/1.1 Host: mark.gruden.int ---------------------------------------------------------- 2. <cflocation> is run and server responds telling the client the resource has moved: ---------------------------------------------------------- HTTP/1.x 302 Moved Temporarily Location: page2.cfm ---------------------------------------------------------- 3. Client goes to fetch the new location http://mark.gruden.int/workspace/Tests/CF/page2.cfm --------------------------------------------------------- GET /workspace/Tests/CF/page2.cfm HTTP/1.1 Host: mark.gruden.int ---------------------------------------------------------- 4. Server responds with a 200 - page found message and the page content for page2.cfm --------------------------------------------------------- HTTP/1.x 200 OK --------------------------------------------------------- So is that client side or server side? Well the server tells the client - "I'm not going to give you page1.cfm go get page2.cfm instead." - the client then goes off and fetches page2.cfm. I 'd call that server side. -- Mark Stanton Gruden Pty Ltd http://www.gruden.com --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
