(Another thing you could try, to confirm the nature of the problem, would be to go to the command line on your OS and do a "ping localhost" to see how that resolves. Please go add your vote and/or comments to it. (And you may find that that and 127.0.0.1 are already there).Īgain, I have filed a bug report for this problem. That's the conversion of your localhost request into that IP as it arrives at the server.Īnd again the second issue is that THAT is what CF receives and compares to the ColdFusion Admin "debugging ip addresses list", and for some reason (even in CF2018, and earlier) if you put in "::1" as a value in that field, it converts it to 0:0:0:0:0:0:0:1. You will find that the value shown for the "remote_addr" in the CGI scope is ::1. If there are other IP addresses already there, separate it from the others with a comma. Then in the original file, find the "iplist" value (which lists any debugging ip addresses that have been added in the CF Admin). If you're going to do that, make a copy of the file first, which is found in the \cfusion\lib folder). Until Adobe fixes that issue, a workaround is for you to edit the neo-debug.xml file for your CF setup. I have a workaround for that, editing the neo-debug.xml.Īdobe could fix that last problem (and I have filed a bug report, CF-4203295), but until they do, here's a workaround and explanation of things.Īnd this latter point, of the inability of the Admin to accept ::1-and on the matter of editing that file-is the real focus of this post. But you will find that if you try that, it will change to "0:0:0:0:0:0:0:1", which does not solve this problem. But another would be that if you knew about your localhost calling with the ipv6 address of ::1, you should be able to add that to your CF Admin "debugging ip addresses list" (or use its "add current") button.One option could be to edit your hosts file to force 127.0.0.1, and that should work.In brief, the problem happens when the OS you're working on processes your "localhost" request via ipv6 (if it makes the request as ::1), rather than ipv4 (as 127.0.0.1). This is a problem that has troubled many CF users for some years (especially as they have moved to later operating systems): they find that ColdFusion debugging output does NOT appear to them when testing using a URL with "localhost" for the domain name but it DOES appear if they use the 127.0.0.1 ip address instead.Īnd sure, they could change to just using the ip address, but they wonder why it fails with "localhost" and whether they can fix things so that it does? In this post, I offer the explanation and solution. And I may revise the content as necessary. Corrections are welcome, in the comments. Same with links and subsequent comments from myself or others. Some content may be outdated-though not necessarily.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |