> folks use cfheader themselves to accomplish the redirect,
> which is similar to using cflocation. The difference is that
> with a cfheader tag (I think it's "status" with a value of
> "302" but that's not really my forte) won't also terminate
> the request, so the request would then continue on to deliver
> the file in theory. Though I don't personally know if the
> cfcontent tag will also change the status header that's
> required for the relocation or if there might be other
> complications owing to the standard or implementation of
> HTTP, since the cflocation tag officially creates a "these
> aren't the files you're looking for"
> message and sends the browser on to another place to get them
> -- so the webserver and/or browser may (or may not) interpret
> the cfcontent'ed file as being "not the file you're looking
> for" and not download the file.
When you use CFCONTENT to deliver a file, it doesn't set a Location header.
It simply delivers the content specified by the tag.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
