tracker issue : CF-3791392

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

Support /api as a context path for RESTful web services.

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): / ext-user (Paul Nibin K J)

Created: 07/18/2014

Components: REST Services

Versions: 11.0

Failure Type: Enhancement Request

Found In Build/Fixed In Build: latest build /

Priority/Frequency: Trivial / Unknown

Locale/System: English / Windows 8 64-bit

Vote Count: 0

Currently, the context path of the REST services are /rest. If the user wants he can go and modify the web.xml to a new value. 

But we need to provide /api in default. So we will have support for /api and /rest both.





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

Watson Bug ID:	3791392

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



Supporting both /rest and /api for the REST Servlet mapping.
Comment by Paul N.
11603 | July 18, 2014 08:20:16 AM GMT
Hi Paul, Can you also please support UPPERCASE /REST and /API (by simply adding these 2 to so that REST URLs will still work if user has CAPS LOCK on or if URL was in UPPERCASE? Thanks!, -Aaron
Comment by External U.
11604 | November 16, 2014 02:32:56 AM GMT
The earlier addition of uppercased extention for .cfm and .cfc was done to keep the backward compatibility. For REST, there is no such issue. This would not be done.
Comment by Rupesh K.
11605 | November 24, 2014 09:18:00 AM GMT
Hi Rupesh, 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.
11606 | June 24, 2015 09:32:54 AM GMT
Aaron, as per the HTTP spec, the URL is not case insensitive. So there is nothing that needs to be done here.
Comment by Rupesh K.
11607 | June 24, 2015 09:44:21 AM GMT
It's kind of sad to read the original request above and think that the team responded to it, adding /api as a new "reserved URL", thus breaking any apps of people moving to CF11 or 2016 who already had an /api folder in their web site. Now THEY have to edit the web.xml file to REMOVE that /api servlet-mapping. It seems the people WANTING something other than /rest are the ones who should have been left to MODIFY it.
Comment by Charlie A.
27585 | April 14, 2018 07:17:39 PM GMT