serverless-functions

Is your feature request related to a problem? Please describe.
Currently, there are two ways to create HTTPTrigger using the fission command.

1. fission fn create with below parameters

  --url=''                              URL pattern (See gorilla/mux supported patterns)
  --prefix=''                           Prefix with which functions are exposed. NOTE: Prefix takes
    

Environment details:

• local deployment (standalone openwhisk)

Steps to reproduce the issue:

1. create a web action using this function:

> cat t.js
const main = () => ({
  "body": {
    "message": "hello"
  },
  "statusCode": 442
})

2. invoke the web action

> wsk action update t t.js --web true
> curl -X POST `wsk action get t --url`
{
  "code": "b86c3c

this will very quickly get out of hand if we allow it, i realize we don't have principles written down anywhere but to date one of them has been that binaries 'just work' without having to do any configuration. currently a user must set FN_MAX_REQUEST_SIZE, FN_MAX_RESPONSE_SIZE -- neither of these should be required to run.

test case:

cd tests/fn-system-tests/
go test -v

this

Rate limit

Just spent an embarrassing amount of time trying to determine why the wsk CLI was working on one machine and not on another. The ultimate issue was that I ended up specifying the APIHOST variable as https://localhost:8443/ in the config file, with the trailing slash, which causes 404s since the CLI was sending requests to https://localhost:8443//api/v1/namespaces/_/triggers?limit=0&skip=0 (n