The Twine forums are now archived. If you need help, please visit

HTTP [POST] Persistence in the Ruleset?

I have a HTTP [POST] rule for my Twine that connects to a API logger when vibration is detected.  The rule works great and is fully functional when loaded on the device.  When I go back into the rule through the UI it always defaults back to [GET] and I have to use the drop down to get [POST] again.  Is this the designed behavior or should the UI be selecting that last-know-load from the device?

Thanks in advance,

Best Answer


Sign In or Register to comment.