Conflict sending data to hosted Emoncms servers

[HLFCode]

I raised this issue in Emoncms where using GET rather than POST was causing problems sending data to Emoncms. POST rather than GET should be used here to avoid the problem

Our server was shutting us down because the url has the word apikey in it and this broke an allowed words rule. [apikey is also an fake wordpress plugin apparently]

It can be avoided using POST with the apikey (and other data) as POST parameters Note that something not in the Emoncms docs is that the POST headers need to be ‘content-type’: ‘application/x-www-form-urlencoded’

Thanks Mike

[jeremypoulter]

Think that change is fine but should clarify when it was implemented to see what if any backwards compatibility issues there may be