What consumes your web service? I would think that, at least when in production, it will not be you typing URLs in the browser's location bar, but rather, an application that uses some sort of HTTP component to initiate the request to your FoxWeb server. Virtually all HTTP components can send data via post. The exact method varies, so consult the documentation of the component you plan to use.
On the FoxWeb side you can retrieve the complete POST data, by calling the Request.Form() method with no parameters.
Sent by Gabriel Badea on 12/13/2008 11:35:34 AM:
I have written a homegrown version of a web service using FoxWeb.
I use a normal query string (i.e. http://.../ws.fwx?service=someservice&function=somefunction&appkey=ABCD-12345678-FDB7¶m1=... well... you get the idea) to run some process defined by the querystring field/value pairs and return an XML response (i.e. Response.ContentType = "text/xml"). There is a severe limitation to this way of doing things if the querystring is long and exceeds the maximum length for a query string (some say 2048 bytes others 4096 etc...)
1. How would I go about sending an xml string using the POST method?
2. I noticed that once in a while one or more channels die and do not get restarted (i.e. if I check show_channels.fwx I'll only see channels 1-3, 5-7 and 9-10). Waiting for them to restart didn't help as I . It happens only occasionnally and I have to restart Foxweb to fix the problem. I'm running version 3.51 as a service with 10 channels.