tracker issue : CF-3917048

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

[ANeff] Bug for: CF file extensions still case-sensitive in SES URLs

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

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

Created: 01/07/2015

Components: Installation/Config, Connector

Versions: 11.0

Failure Type:

Found In Build/Fixed In Build: CF11_Final /

Priority/Frequency: Major / Some users will encounter

Locale/System: ALL / Platforms All

Vote Count: 0

Listed in the version 2016.0.0.297996 Issues Fixed doc
Verification notes: verified_fixed on February 18, 2019 using build 2016.0.01.298513
#3199283 only partially fixed the case-insensitivity of CF file extensions. As mentioned in #3199283, the "/" after the file extensions still trigger 404s for the following, but shouldn't:


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

Watson Bug ID:	3917048


External Customer Info:
External Company:  
External Customer Name: itisdesign
External Customer Email:  
External Test Config: Verified w/ CF11 Update 3 Standalone Enterprise on x64 Windows 8.1 Pro w/ IIS



All the missing extensions have been added except for anything related to "rest" APIs. Since "rest" is like a keyword in the URL, it is required to be present in correct case.
Comment by Chinoy G.
9064 | January 26, 2015 11:46:11 PM GMT
Hi Chinoy, Yes, I understand "rest" is a special case. However, I have seen elderly people type URLs w/ their CAPS LOCK on. Can a web.xml & rule please also be added for /REST/*? Thanks!, -Aaron
Comment by External U.
9065 | January 27, 2015 12:36:36 AM GMT
Adobe, Should elderly be punished with 404 if they mistakenly have CAPS LOCK on when typing a REST URL? I believe the answer should be "no". Thus, REST should be allowed as UPPERCASE. Thanks!, -Aaron
Comment by External U.
9066 | January 28, 2015 05:57:53 PM GMT
Comment by External U.
9067 | January 31, 2015 12:47:11 PM GMT
Closing the bug as fixed. Case insensitivity for CFM, CFML, CFC, CFR and CFSWF are handled. /REST/ will not be handled as discussed in bugs CF-3917003 and CF-3791392.
Comment by Immanuel N.
9068 | June 24, 2015 04:25:41 AM GMT
Hi Immanuel, Thanks. I've added the following comment to those tickets: Elderly type w/ CAPS LOCK on, regardless of CF version. For that reason, it makes sense to also support "/REST". Thanks!, -Aaron
Comment by External U.
9069 | June 24, 2015 09:35:46 AM GMT
Hi Adobe, I've verified this is fixed in CF2016 Update 1 (build 2016.0.01.298513). The correct entries were added to web.xml. Well, aside for /REST/* ;) Thanks!, -Aaron
Comment by Aaron N.
30312 | February 18, 2019 09:20:19 AM GMT