We have several templates in a legacy code base where scheduled tasks call
scripts that perform a CFHTTP to another template which itself contains a
cflocation.
we have redirect=“yes” on the cfhttp call but unlike on CF 9.01 (and
previous versions of cf) where this has run fine for years. The
CFTTP.filecontent is consistently logging
the 302 status with the filecontent containing only
Document Moved
Object
Moved
here
The docs says this will happen when the redirect is more than 4 OR
redirect=no" which i am sure is NOT happening in our case
ColdFusion follows a maximum of four redirects on a request. If there
are more, ColdFusion functions as if redirect = “no”.
Anybody know what this could be?
After posting the above issue, i came across this
https://groups.google.com/forum/#!searchin/lucee/cfhttp$20redirect/lucee/yOekZqkLWXo/uGRZ1p6iBQAJ
I assume this is exactly what we are experiencing.
But, why would this have worked in ADC for the past 10 years?On Monday, April 18, 2016 at 10:44:02 AM UTC-5, Scott Conklin wrote:
We have several templates in a legacy code base where scheduled tasks call
scripts that perform a CFHTTP to another template which itself contains a
cflocation.
we have redirect=“yes” on the cfhttp call but unlike on CF 9.01 (and
previous versions of cf) where this has run fine for years. The
CFTTP.filecontent is consistently logging
the 302 status with the filecontent containing only
Document Moved Object
Moved
here
The docs says this will happen when the redirect is more than 4 OR
redirect=no" which i am sure is NOT happening in our case
ColdFusion follows a maximum of four redirects on a request. If there
are more, ColdFusion functions as if redirect = “no”.
Anybody know what this could be?