Hi All,
I'm on CF 4.5
I wanted to do some 404 processing so that I can make cool looking urls that route to
the proper destinations. So I had my host get into CF admin and change the 404 errors
to be sent to a cfm page. we specified "URL" so that the file would get processed.
But I found that when we did that, CFLocation tag stopped working reliably. So I
wrote my own... here's the gist:
<cfheader name="location" value="#attributes.url#">
<cfheader statusCode="302" statusText="Document Moved">
Seems to work just fine. I plan to add the "addToken" param later. But does anyone
see anything wrong with what I've done? Can anyone forsee any future complications?
Mainly just sharing my knowledge, cause I asked and no one seemed to know why
CFLocation started acting funny.
JGG
--
These lists are syncronised with the CFDeveloper forum at
http://forum.cfdeveloper.co.uk/
CFDeveloper Sponsors and contributors:-
*Hosting and support provided by CFMXhosting.co.uk* :: *ActivePDF provided by
activepdf.com*
*Forums provided by fusetalk.com* :: *ProWorkFlow provided by proworkflow.com*
*Tutorials provided by helmguru.com* :: *Lists hosted by gradwell.com*
To unsubscribe, e-mail: [EMAIL PROTECTED]
