tracker issue : CF-3791396

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

Make HTTP Methods optional, if the function names itself are GET, POST, PUT or DELETE

| 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 release /

Priority/Frequency: Trivial / Unknown

Locale/System: English / Win XP All

Vote Count: 2

Currently the HTTPMethod is mandatory attribute, if you want to make a function as a resource.

We should make the HTTPMethod attribute optional, if the name of the function is GET, POST, PUT or DELETE.





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

Watson Bug ID:	3791396

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



If the function names are GET/POST/PUT/DELETE/HEAD/OPTIONS, no need to specify the HTTPMethod attribute. The HTTPMethod will be infered from the function name. Should check other conflicting scenarios as well. If the function name is "get", but HTTPMethod is explicitly specified as "POST", then the POST will be used.
Comment by Paul N.
11599 | July 18, 2014 08:24:13 AM GMT
Good idea! -- Adam ////////////////
Vote by External U.
11600 | July 19, 2014 04:01:15 AM GMT
+1 ......................
Vote by External U.
11601 | November 16, 2014 02:34:36 AM GMT