Executing GET (or any other HTTP verb) on a URL

[yuigoto]

Hi! Newbie here, I'm still on the Flowstone trial to see if it fits the type of work I want to do here.

Been eyeing the tool since it was called SynthMaker and now I'm having the opportunity to properly try it.

So, I'm trying to build a small trigger for a webserver I manage here and I stumbled upon a small problem: searching through the application, I found that we do have a Http POST object, and it works pretty well here, but my web server uses different verbs for requests, and I need to do some GET requests sometimes, is it possible?

If no module is present for this type of request, then how can I make it work? Should I use Ruby for that?

Thanks!

[trogluddite]

Hi, yuigoto! I don't have an easy answer to your problem, I'm afraid, but I though I'd at least welcome you to the forum.

I think you're right that Ruby would be the way to go, but unfortunately, I don't think that'll be easy. The version of Ruby in FlowStone doesn't include the "standard libraries" that stand-alone Ruby normally ships with, which would include the Net::HTTP class which I think would be ideal for your needs.

In principle, it is possible to extend FlowStone's Ruby with additional libraries of classes and modules, but there's a caveat - if they are compiled from C++ code, they must have been compiled with Microsoft's Visual Studio, which unfortunately is rare for downloadable Ruby extensions. Someone did post here a version of the Ruby standard libraries compiled in this way, but sadly, my searching has only turned up dead links (if anyone else knows where we can find this, please let us know!)

[yuigoto]

Thanks, trogluddite! I kinda knew it would be like this in the end.

I'll see what I can do here, but going this way is kinda the opposite of what I wanted to do, since I kinda wanted to do it the simple way hahaah

I might have to work on an endpoint using POST until a better possibility appears.

Thanks again!

[wlangfor@uoguelph.ca]

Thanks, trogluddite! I kinda knew it would be like this in the end.

I'll see what I can do here, but going this way is kinda the opposite of what I wanted to do, since I kinda wanted to do it the simple way hahaah

I might have to work on an endpoint using POST until a better possibility appears.

Thanks again!

there is also some primitives. A lot is possible if you retrofit.