Manually Fire an HTTP request (for Testing)

Kit Plummer

It'd be really nice to be able to fire off an HTTP request to test the receive side hook.

John Kestner

Give it a shot now.

Kit Plummer

I see the button, and I've clicked it. But, I don't know if it's not firing or I'm not receiving it. I have a rule for temperature and that seems to send the request. I have rules for orientation changes - which don't. Hmmn. Maybe my rules just isn't any good.

Kit Plummer

Oh, I see. Only the first "When,Then" box works. If I click the second "Test URL" button, the first box's button turns ready and says Error.

Kit Plummer

I also noticed that the URL that is GET'd isn't complete, it's truncating everything after the first parameter (everything from & on). Thanks for working this...good stuff.

Tim Stoute

I'm also finding that with the" Test Url" button the on the HTTP request config, the second name value pair on the query string is not being passed. Any insight on this? My url looks like this:

http://x.appspot.com/?datatype=move&v=[shaking/still]

But only sends:

http://x.appspot.com/?datatype=move

Joel Finkle

This is a known issue. If the receiver of your message can interpret a JSON-formatted string, you might be better off.

See http://en.wikipedia.org/wiki/Json#Data_types.2C_syntax_and_example

Example: http://x.appspot.com/?data=("datatype":"move","v":"shaking")

Matt Dorn

Has this been corrected? I am trying to pass an url to notifymyandroid.com:

https://www.notifymyandroid.com/publicapi/notify?apikey=xxxx&application=Twine&event=Garage is OPEN!&description=A garage door is now OPEN. The temperature is [temperature].&priority=1

It works perfectly when I try it in the browser but does not work with HTTP GET and the parameters section is too limited for POST.  The api does not support JSON.