romkey
changed http call to IFTTT to use POST instead of GET
The GET implementation does not support values with spaces. The workaround would have been to percent-escape the value strings (replace spaces with %20, etc.), which is the approach intimated by the urlencode branch. The HTTPClient library however doesn't includes a method for this, and IFTTTWebhook is not the right place to implement it.
A better approach I believe is to use POST instead of GET, and pass the values as JSON payload. Aside from not having to percent-encode the values, this has the added benefit of dismissing future issues around maximum length for the values, constraints by the size limit of the URL supported by the IFTTT webserver (unknown by me, but certainly limited). POST may also have added security benefits.
A side-effect of this change is the incompatibility of HTTPS POST using the root cert, so I'm proposing to revert to the fingerprint approach which works fine. (The root cert approach worked fine with GET on my ESP2 Dev Module board, possibly an issue with the WiFi library? I didn't dig deeper, fingerprint works.)
This patch, if accepted, resolves issue #8 and renders redundant the outstanding work on urlencode branch.
Hey @14geronimo this looks great, thank you! Sorry for not seeing it (and the issues I just read) sooner, github hasn't been sending me notifications about this stuff :( I need to do a little testing over the next couple of days and then I'll merge.
That's very curious about the root cert issue... I'll look into that too, but I won't hold up merging and updating for it.
Awesome of you to contribute, thanks!
