tracker issue : CF-3199283

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

file extensions case-sensitive on all web servers

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff (Aaron Neff)

Created: 05/27/2012

Components: Web Container (Tomcat)

Versions: 10.0

Failure Type: Usability Issue

Found In Build/Fixed In Build: Final / 282661

Priority/Frequency: Minor / Some users will encounter

Locale/System: English / Platforms All

Vote Count: 5

Related Bugs:
CF-3307421 - Similar to


In CF10, file extensions are case-sensitive in all web servers (built-in, Apache, IIS, etc).

This causes a backward-compatibility issue for users that may type an address w/ CAPS LOCK on.  This also affects the "/rest/" portion of CF10 Rest URLs.

The solution is simple:  Just add uppercase servlet mappings to web.xml and uriworkermap.properties.

web.xml example:

<servlet-mapping>
    <servlet-name>CfmServlet</servlet-name>
    <url-pattern>*.CFM</url-pattern>
</servlet-mapping>
<servlet-mapping>
    <servlet-name>CfmServlet</servlet-name>
    <url-pattern>*.CFML</url-pattern>
</servlet-mapping>
<servlet-mapping>
    <servlet-name>CFCServlet</servlet-name>
    <url-pattern>*.CFC</url-pattern>
</servlet-mapping>
<servlet-mapping>
    <servlet-name>CfmServlet</servlet-name>
    <url-pattern>*.CFM/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
    <servlet-name>CfmServlet</servlet-name>
    <url-pattern>*.CFML/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
    <servlet-name>CFCServlet</servlet-name>
    <url-pattern>*.CFC/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
    <servlet-name>CFRestServlet</servlet-name>
    <url-pattern>/REST/*</url-pattern>
</servlet-mapping>

uriworkermap.properties example:

/*.CFM = cfusion
/*.CFML = cfusion
/*.CFC = cfusion
/*.CFM/* = cfusion
/*.CFML/* = cfusion
/*.CFC/* = cfusion
/REST/* = cfusion

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

Watson Bug ID:	3199283

External Customer Info:
External Company:  
External Customer Name: itisdesign
External Customer Email:

Attachments:

Comments:

Related thread: http://prerelease.adobe.com/r/?11dc2c8ee4d94eb185cdab434687e532
Comment by External U.
19163 | May 27, 2012 12:54:29 AM GMT
Here is Rob Brooks-Bilson's paper on this issue: http://bit.ly/LvZlyX
Comment by External U.
19164 | May 27, 2012 12:56:12 AM GMT
+1. Must be fixed ASAP. -- Adam
Vote by External U.
19172 | May 28, 2012 01:01:10 AM GMT
Agree, this is a serious change in behavior that's unexpected. Especially on IIS, where this has never been an issue.
Vote by External U.
19173 | June 04, 2012 07:10:26 AM GMT
I added the fix lines from above and still cannot get CFM to operate
Comment by External U.
19165 | January 03, 2013 02:09:32 PM GMT
This is a major issue for me and I am really stuck between a rock and hard place at this point. Please fix this issue ASAP.
Vote by External U.
19174 | July 14, 2013 10:45:18 PM GMT
How is this marked as fixed in build 282661, when it is still an issue in 285437? Am i missing something? I would love to see this fixed.
Vote by External U.
19175 | October 03, 2013 11:14:51 AM GMT
Like others have said this still isn't fixed and should be.
Vote by External U.
19176 | November 07, 2013 10:41:40 AM GMT
Adobe, This is only *partially* fixed in Splendor Public Beta. UPPERCASE SES & REST URLs still aren't fixed. These are still missing in web.xml & uriworkermap.properties: 1) /*.CFM/* 2) /*.CFML/* 3) /*.CFC/* 4) /REST/* For completeness, these should also be added: 5) /*.CFR 6) /*.CFSWF Can this ticket please be re-opened? Thanks!, -Aaron
Comment by External U.
19166 | February 28, 2014 02:50:24 AM GMT
The below mentioned cases will be tracked and fixed as part of bug CF-3917048.
Comment by Immanuel N.
19167 | January 09, 2015 06:07:00 AM GMT
Hi Immanuel, All 6 cases? B/c CF-3917048 only mentions cases 1-3. Should I add cases 4-6 to CF-3917048? -Especially- want to confirm that case #6 (/REST/*) would be included. Thanks!, -Aaron
Comment by External U.
19168 | January 09, 2015 02:50:14 PM GMT
Not to worry Aaron! All 6 cases will be taken care of.
Comment by Immanuel N.
19169 | January 11, 2015 11:32:46 PM GMT
/REST/* was never taken care of. Makes no sense to not allow /rest/*
Comment by External U.
19170 | November 23, 2015 03:49:36 AM GMT
[correction] /REST/* was never taken care of. Makes no sense to only allow /rest/* and not /REST/*
Comment by External U.
19171 | November 23, 2015 03:50:27 AM GMT