tracker issue : CF-3630245

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

Path in 404 on non existing *.cfm is reported as /jakarta/isapi_redirect.dll

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Thomas Gorgolione / Thomas Gorgolione (thomasvg1)

Created: 09/11/2013

Components: Web Container (Tomcat)

Versions: 10.0

Failure Type:

Found In Build/Fixed In Build: Final / CF10_Update14

Priority/Frequency: Major / Unknown

Locale/System: English / Win 2008 Server R2 64 bit

Vote Count: 10

Problem Description: A 404 error on a non existent ColdFusion page will have it's path reported as /jakarta/isapi_redirect.dll.  Custom 404 pages cannot ascertain the actual page the user asked for.  404s on items that aren't *.cfm do not have this issue (although I haven't tried this on *.cfc's)

Steps to Reproduce: Set up a custom 404 cfm page that dumps the CGI variables.  Type in a random non existent cfm, like asdf.cfm, and see what returns for the CGI path variables

Actual Result: Returns as /jakarta/isapi_redirect.dll

Expected Result: Should return as the path and filename of the non-existent page

Any Workarounds: Have a URL redirector receive requests before they hit ColdFusion, and configure the URL redirector forward any missing page/directory requests to a specified custom 404 page.  Basically have the redirector handle 404 routing.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3630245

Keywords:
FixTested


External Customer Info:
External Company:  
External Customer Name: thomasvg1
External Customer Email:  
External Test Config: My Hardware and Environment details:



Test Environment

ColdFusion 10 with Update 11

Windows 7 x64 with IIS 7.5

SQL Server 2005

8GB RAM

Java 7 Update 25



Live Environment

ColdFusion 10 with Update 11

Windows Server 2008 R2 x64

SQL Server 2005

16GB RAM

Java 7 Update 25

Attachments:

Comments:

URLs of forum posts/Stack overflow users who are having this problem: http://stackoverflow.com/questions/18694932/coldfusion-10-iis-non-existant-urls-that-are-cfm-files-retrieving-original-u http://stackoverflow.com/questions/DVAMC-17956552/coldfusion-10-iis-7-5-and-custom-404-page http://forums.adobe.com/message/5557172
Comment by External U.
14538 | September 11, 2013 09:21:47 AM GMT
I have seen many questions about this issue.
Vote by External U.
14546 | September 11, 2013 10:46:45 AM GMT
This bug resulted in us having to cook our own URL Rewrite workaround, so that requests such as the ones described in this bug are passed to the 404 handler, before they are passed to the isapi_redirect module. ColdFusion 10 Update 11 Windows Server 2012 R2 (IIS8)
Vote by External U.
14547 | September 12, 2013 02:14:06 AM GMT
Seeing this same issue. Please fix.
Vote by External U.
14548 | September 12, 2013 02:20:38 AM GMT
Identical issue here. I traced it by turning on IIS Failed Request Tracing Rules and set it as noted below. The trace files list the url as http://[domain_name]:80/jakarta/isapi_redirect.dll Here is the trace rule config <tracing> <traceFailedRequests> <add path="*"> <traceAreas> <add provider="ASP" verbosity="Verbose" /> <add provider="ASPNET" areas="Infrastructure,Module,Page,AppServices" verbosity="Verbose" /> <add provider="ISAPI Extension" verbosity="Verbose" /> <add provider="WWW Server" areas="Authentication,Security,Filter,StaticFile,CGI,Compression,Cache,RequestNotifications,Module,FastCGI" verbosity="Verbose" /> </traceAreas> <failureDefinitions statusCodes="404" /> </add> </traceFailedRequests> </tracing>
Comment by External U.
14539 | September 17, 2013 10:10:29 AM GMT
See attached note. Same problem here.
Vote by External U.
14549 | September 17, 2013 10:11:19 AM GMT
We have encountered this as well. We had requests to http - port 80 redirecting to https - port 443 through IIS with CF 9. Trying same setup in CF 10 results in redirect to https://domainname/jakarta/isapi_redirect.dll
Vote by External U.
14550 | September 23, 2013 10:06:23 PM GMT
We have this same issue on our CF10 box. This extremely hampers this server. If anyone needs any more info I'd be happy to help.
Vote by External U.
14551 | October 31, 2013 08:18:35 AM GMT
Same problem here. Same setup. We built a new CF10 box specifically to move old sites off a retired server and until we get the 404 working we cannot move these sites.
Vote by External U.
14552 | October 31, 2013 09:43:47 AM GMT
This issue is very frustrating... we've migrated back to ColdFusion 9 for the time being. Hopefully the CF Development team will fix this issue.
Vote by External U.
14553 | December 04, 2013 02:31:01 PM GMT
Please fix this for SEO.........
Vote by External U.
14554 | January 08, 2014 09:13:59 PM GMT
Please fix it, this issue creates great problems :(
Vote by External U.
14555 | January 17, 2014 08:03:08 AM GMT
So where does this bug stand? Support told me over the phone that there are still problems even after they pushed the fix out to "Selected Users".
Comment by External U.
14540 | March 10, 2014 09:36:32 AM GMT
I am following another 404 bug, CF-3488063. The fix for the CF-3488063 bug still has problems and may be what Support is referring to.
Comment by External U.
14541 | March 10, 2014 10:44:36 AM GMT
This bug is marked "fixed", but when will it be relased? Will it be released for CF10? or only CF11?
Comment by External U.
14542 | March 21, 2014 11:14:31 AM GMT
Having the exact same issue under IIS7 / CF11 I'd like to add that this issue doesn't exist under IIS6 / CF10, so my understanding is that this *might* be either an IIS7 issue or an IIS7 "feature" and thus nothing to do with CF...
Comment by External U.
14543 | December 01, 2014 08:36:03 AM GMT
As mentioned before by @thomasvg1, there's a fix for this problem and I can confirm it works fine! http://stackoverflow.com/questions/18694932/coldfusion-10-iis-non-existant-urls-that-are-cfm-files-retrieving-original-u
Comment by External U.
14544 | December 01, 2014 08:37:32 AM GMT
We have a fix for Bug CF-3488063. Please send an email to cfinstal<AT>adobe<DOT>com to get the fix.
Comment by Anit K.
14545 | December 01, 2014 08:41:45 AM GMT