Feature Request: Add `GET` portion to new HTTP api

[mark-epstein]

Is this a feature relevant to companion itself, and not a module?

• [X] I believe this to be a feature for companion, not a module

Is there an existing issue for this?

• [X] I have searched the existing issues

Describe the feature

Don't remove the HTTP GET requests, particularly those that set custom variables. The documentation give no specific deadline, but rather leaves it open for my anxiety to interpret.

I understand the stated rationale of trying "to follow REST principles, and the convention that a POST request will modify a value, and a GET request will retrieve values." I'm asking that unless there is a compelling reason other than to adhere to these principles, that the legacy commands be allowed to remain.

Usecases

Sending a POST request is more difficult. Perhaps only minimally so, but I like that I can email a string to someone non-technical. have them paste that string in a browser address bar, and they're done. I use this to actuate buttons on pages they can't reach from the Stream Deck, or to set variables.

I make extensive use of PowerPoint's ability (via IrisDown's RSC) to launch web requests, so that slides in my presentation will trigger companion events. These are invaluable for keeping PowerPoint and Companion in sync instead of requiring a user to advance a slide and press one or more Companion button(s) simultaneously. GET requests are the only type Remote Show Control supports.