Use proper proper REST Methods (POST PUT or PATCH) and send payload normally

[kpconnell]

Is your feature request related to a problem? Please describe.
Encoding the request payload as a GET is extremely obtuse and makes creating new clients difficult and non-intuitive for other developers.

Describe the feature you'd like
Instead decoding the request in the Lambda, re-factor the API gateway implementation to pass along the payload json so that the API supports either POST or PUT as the verb and a normal JSON payload.

Additional context
Encoding payload in GET instead of using url parameters, as well as using GET for something that modifies data goes against RESTUL conventions in general.

[simonkrol]

Hi @kpconnell,

I don't agree with this, any request made to SIH is retrieving a resource, which feels like exactly the use case for a GET request. Making a request with edits doesn't modify any data, it retrieves the requested image, generating it if required. As well, we're using CloudFront to cache responses to these requests in order to prevent having the Lambda generate image for duplicate requests, which wouldn't be possible with POST or PUT requests.
I'm going to close this issue for now, but feel free to re-open if I've missed or misunderstood anything,

Thanks for your interest in Serverless Image Handler,
Simon

[kpconnell]

You may disagree with which verb, (this DOES create data which you agreed to) but even if you like your GET , why not use proper query string parameters like the rest of the world does?

[simonkrol]

Hi @kpconnell,
That is something we're considering, it is tracked over at #184.
Thanks,
Simon