tracker issue : CF-4205361

select a category, or use search below
(searches all categories and all time range)

CF2016 - intermittent 404 after Update 12

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/Duplicate

Reporter/Name(from Bugbase): Kyohei Y. / ()

Created: 10/02/2019

Components: Installation/Config, Connector

Versions: 2016

Failure Type: Incorrectly functioning

Found In Build/Fixed In Build: 315717 /

Priority/Frequency: Normal / Most users will encounter

Locale/System: English / Win 2016

Vote Count: 3

Problem Description:  
ColdFusion 2016,0,12,315717
Windows Server 2016
IIS 10
My IIS root directory contains an index.cfm, which is displayed when I navigate to http://localhost because index.cfm is set to be the IIS default page. After installing the recent Update 12 on ColdFusion 2016 AND recreating the connector, accessing the root URL occasionally returns a 404 not found error, instead of serving the index.cfm file that exists.
Note that this does not happen all the time, but is intermittent. For example, I could reload http://localhost 10 times, and perhaps 3 of those requests will return a 404, while the other requests will properly display the index.cfm.

Navigating to http://localhost/index.cfm (with the filename) always works, and never returns a 404 error.  
Each time the incorrect 404 is returned, the isapi_redirect.log contains the following entry:  
[warn] jk_check_for_path_attack::jk_util.c (2457): Path attack using [/]  
This issue is similar to the admin page 404 issue in CF-4205252 (I'm opening this new issue because I'm not seeing this issue on the admin page) as well as the 404 issue discussed in the comments of  
Steps to Reproduce:    
-Install Update 12 on ColdFusion 2016 running on IIS 10  
-Rebuild connector  
-Repeatedly hit the server root URL and observe returned HTTP status codes  
Actual Result:  
Many requests fail with status code 404.  
Expected Result:  
All requests return the index.cfm contents with status code 200.  
Any Workarounds:  
None found.



We are having this issue as well, have verified on multiple servers running CF 2016. The problem exists with update 12, not with update 11
Vote by Don W.
31539 | October 03, 2019 08:13:23 PM GMT
This is also happening in CF 2018 HF 5
Comment by Toby W.
31547 | October 04, 2019 03:45:11 PM GMT
I'm surprised there has been no response from Adobe to this. I will note that they did create an updated connector DLL for another bug, as reported (for now) only in a thread in the forums, where they also offered a link to download a new isapi_redirect.dll. It's not clear if it's the same problem as this one, but it may be. Check out, which says: "We have a patched isapi_redirect.dll which you can use. Its placed in: Please let me know if this solves your issue. You need to goto [CF Home]\config\wsconfig\[Magic folder for your connector] Make a copy of the isapi_redirect.dll file Replace it with the one I shared in the dropbox link Restart the Application Pool for your IIS website Thanks, Kailash" If anyone experiencing this issue reported here wants to try it, to see if it makes the problem go away, please do then report here how it goes, or perhaps Adobe will soon offer a clarifying comment. I'm just trying to help people juggling all the balls, to get the update in place ASAP, especially for the security fixes it includes.
Comment by Charlie A.
31558 | October 07, 2019 10:35:05 PM GMT
Hi All,   We have patched isapi_redirect.dll and files which you can use to get over the issue. Its placed here: * For ColdFusion 2018:[]  * For ColdFusion 2016:[]    Steps to apply the patch: For IIS: # You need to goto [CF Home]\config\wsconfig[Magic folder for your connector] # Make a copy of the isapi_redirect.dll file # Replace it with the one shared in the dropbox link # Restart the Application Pool for your IIS website For Apache: # You need to goto [Apache Home]\conf directory (for CF2016, this will be at [CF Home]\config\wsconfig[Magic folder for your connector]) # Make a copy of the file # Replace it with the one shared in the dropbox link # Restart the Apache webserver   Even though the patch solves the issue, we still strongly recommend not to use the ColdFusion Administrator using the connector port, but using the internal webserver port (8500 series port)   Thanks, Kailash
Comment by Kailash B.
31560 | October 08, 2019 10:29:27 AM GMT
Thanks for the link, Kailash. Is the Dropbox link you posted the only Adobe fix for this 404 issue? If so, I am wondering why this bug ticket is still in "To Fix" status? Or, is this ticket still in "To Fix" status because there is a ColdFusion update coming that will officially fix this issue? Thanks for the clarification.
Comment by Kyohei Y.
31565 | October 08, 2019 02:14:41 PM GMT
Hi Kyohei,   Yes this is the only fix by Adobe. I had also posted this same fix in one of the forum posts. We will be releasing this as part of a future update of ColdFusion   Thanks, Kailash
Comment by Kailash B.
31571 | October 09, 2019 06:29:10 AM GMT
Reporting back that I have installed the provided isapi_redirect.dll and everything is working great, with no observed 404 errors. Thanks!
Comment by Kyohei Y.
31581 | October 10, 2019 04:44:19 PM GMT
It looks like no one ever reported here that Adobe created a blog post discussing the issue and offering the fix (in a more formal way): While the title implies that it's a fix for those with Admin issues, this is so far the only fix for connector issues since the Sept 24 update (as far as I know), so it seems it should address any known connector issues. It would be nice to hear confirmation from Adobe.
Comment by Charlie A.
31725 | October 30, 2019 04:41:07 PM GMT
I got a notification today about this, regarding a slight change in the "component" it was being tracked under. I assume that was done by an Adobe rep. Coming back to it, I am surprised to see that no one from Adobe ever updated this (with a comment or "fixed in build" indication) that this was addressed with CF2016 update 13, released in Nov 2019, as indicated here: FWIW, this bug report and comments since were all from Oct 2019, the month before it was released. And it seems it has resolved things, as there have been no more comments since then, But a change in the "fixed in build" (currently empty as I write) would be helpful to confirm things for readers. Indeed, instead I see a "withdrawn" indication, though again without any comment from Adobe. Finally, Toby had mentioned above experiencing the same issue after CF2018 update 5. It was released at the same time as CF2016 update 12 (which is what this bug was about), and CF2016 update 6 was released also in Nov (with this CF2016 update 12), so Toby, you should find it has been resolved.
Comment by Charlie A.
33129 | February 15, 2020 09:00:22 PM GMT
@Charlie, this bug was closed as duplicate of CF-4205252. The fixed in build info was updated for bug CF-4205252 at the time of release of updates.
Comment by Vamseekrishna N.
33144 | February 18, 2020 04:09:34 AM GMT