It's weird because I have the same code on 2 servers and it works on one and
not the other. The page that is doing the cflocation is part of a fairly
complex series of <cfif> statements that do various things based on fields
in a database. One of those fields is a filename and the <cflocation> tag is
supposed to call the file from the database. When I replace the <cflocation>
tag with a <meta refresh> it works. And it also works on the other server.
Something must have changed on the demo server to stop it from working but
I'm stumped as to the cause.
I agree with you that it sounds like a confusion in the HTTP status. I'm not
setting any cookies but there is a login routine in the Application.cfc
file.
The thing I'm trying to understand is why it works on one server and not the
other.
-= Ed
> -----Original Message-----
> The 200 is the give-away.
>
> I tried going to your site (from the log line below) and I
> can see this is a login page of sorts.
>
> MX7 is a current revision, so some of those old caveats that
> caused problems aren't in play. But, let's examine the page
> that's supposed to do the CFLOCATION a little closer. I'll
> be happy to look at it (off list even, if you like).
>
> My bet is that you're doing a cfcookie to set some sort of
> login flag, and then do a cflocation.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Create robust enterprise, web RIAs.
Upgrade & integrate Adobe Coldfusion MX7 with Flex 2
http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU
Archive: http://www.houseoffusion.com/groups/CF-Linux/message.cfm/messageid:4237
Subscription: http://www.houseoffusion.com/groups/CF-Linux/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.14
