So I have a simple WebService running - as a Standalone App. The Event 'HandleURL' is being used to handle the requests.
What I don't yet understand is:
How is this supposed to work if the app is being deployed as .cgi?
Let's assume: http://my-ip.address/cgi-bin/myapp.cgi
Running it in Apache2 on Ubuntu works without any issue. I can use it as a regular Xojo WebApp (by opening http://my-ip.address/cgi-bin/myapp.cgi in the Browser).
And I get the app to handle http://my-ip.address/cgi-bin/myapp.cgi/MyCustomRequest (from the "local" Ubuntu machine using Firefox).
However, if I don't get the app to handle http://my-ip.address/cgi-bin/myapp.cgi/MyCustomRequest with 'HandleURL' from another machine (Windows, IE).
Somehow, it also doesn't make quite sense to me: How can Apache2 know that .../myapp.cgi/MyCustomRequest should be handled by the .cgi (and /MyCustomRequest shall be what's going to 'HandleURL'-event)? Why does it know that there's this .cgi, and is not looking for a folder 'myapp.cgi' and another folder 'MyCustomRequest'?
One other idea which I couldn't get to work:
Can I use a Xojo WebApp as .cgi to handle a whole (virtual) "instance"? Configure Apache2 somehow so that all requests are being answered by the .cgi (but of course passing the Request to the same .cgi)?
I only managed to allow a .cgi in the root, so that http://my-ip.address/ launches the Xojo-WebApp.
But http://my-ip.address/MyRequest is then not being passed to the .cgi (along with /MyRequest) - Apache then tried to find an (obviously not existing) index-file in a folder "MyRequest").
How are others doing their WebServices in Xojo? Do you only built them as 'Standalone' or .cgi?
How to design (and how to configure Apache2) it so that it can be used as .cgi, too - getting the .../myapp.cgi/MyRequest -> HandleURL '/MyRequest'?
Or don't I need to bother at all, because a WebService as .cgi is not a good idea anyway - and if so: why?
I know, quite some beginner questions :)
Thanks if you find the time to answer some or all of my questions and/or explain how Xojo WebApp-Services running as .cgi are supposed to work.