Newbie
1 posts
To me, this URL is not performing as you’d expect because, I suspect, it is NOT calling “t1.cfm”:
https://www.skillon.com/cflocation/t1.cfm/
Once you put the slash (/) on the end, your web server is probably thinking you’re trying to calling the ‘default document’ of the directory “t1.cfm”. In many cases, default documents are something like: index.cfm.
So, find out what the default document is on the web server and you’ll know what file is actually being executed.
You seem to be suggesting that if we run those same URLs, we will get what you describe. But I do not. If I run the first one, it stays on t1.cfm and reports a 404 (which seems to be a missing template handler in your app, not just a bare named 404.) But if I visit the second url, I get the same–I never get any infinite loop. And there’s no difference if I change what follows the slash.
Since you describe this as something unexpected, it seems you feel “it was working before”. What has changed for you since it was last working? What CF version are you running now, and what were you running then? If it’s changed, was it on the same machine, and was the url the same before as it is now. Had you recently applied a CF update? If so, what did you go from and what did you go to?
Even if we can’t recreate your problem, perhaps we can surmise what may have happened, depending on what on your end had changed. (If you may want to say “nothing has changed”, again please at least confirm the CF version and update level.)
You must be logged in to post a comment.
22 Sep 2025
Las Vegas, NV
