Lambda + API Gateway: optional proxy param

Question

I've made a Lambda / API Gateway function that has a proxy param as the final param in the URL.

  page:
    handler: handlers/website/getRenderedPage.get
    events:
      - http:
          method: get
          path: /content/{website}/{proxy+}
          cors: true
          request:
            parameters:
              paths:
                proxy: true
                website: true

So, as defined, this is the behavior I'm experiencing:

/content/site.com/blog/hello-world --> website: site.com, proxy: blog/hello-world --> URL works successfully in browser.
/content/site.com --> website: site.com --> URL fails in browser (missing authentication token, aka API resource not found).

Is it possible to make that {proxy+} parameter optional?

Trent Bartlem · Accepted Answer · 2017-06-23 04:58:41Z

3

Just have it listen to two events.

/content/{website} and
/content/{website}/{proxy+}

answered Jun 23, 2017 at 4:58

Trent Bartlem

2,2721 gold badge15 silver badges22 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Kristian Over a year ago

That's what I've been doing, but I recently ran into resource limits in my CF template, so I was hoping to eliminate a few endpoints

Trent Bartlem Over a year ago

Well, the / means you need to separate them. What happens if you call /content/site.com/ instead?

Collectives™ on Stack Overflow

Lambda + API Gateway: optional proxy param

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related