Hi mplaza,
That random parameter worked!!!! Didn't need to use Msxml2.ServerXMLHTTP.
BTW, is there much difference in Msxml2.ServerXMLHTTP against Msxml2.XMLHTTP?
Thanks so much
and thanks to Olaf too with all the help!
@mplaza - thanks for replying.
It's actually the GET rather than the POST which has cacheing issues.
I changed the line from
loRequest.Open("GET", "https://api.parse.com/1/classes/GameScore/abc123456")
to
loRequest.Open("GET", "https://api.parse.com/1/classes/GameScore/abc123456", .f. )...
Hi Olaf,
I turned off the IE manual settings that I had changed to originally 'fix' the cache issue and tried the following code but it did not work :
loRequest.SetRequestHeader('Cache-Control','max-age=0')
loRequest.SetRequestHeader('Cache-Control','no-cache')...
Hi Olaf,
There definately isn't any cacheing done server side as my CURL/PYTHON/LUA scripts all work fine after I manually edit the data server side. It is purely the Foxpro GET that is caching.
I had a very quick look at your link and think I would need to set : Cache-Control: max-age=0...
Hi Olaf,
Got the POST and the GET working as per your code - thanks.
However, the GET doesn't work correctly in that the result seems to be buffered. i.e. The first tine I issue the GET then the ResponseBody has the correct data. If i then go to the Parse Back end and manually update the data...
Hi Olaf,
Thanks for the reply - I will check out your sample code and run it shortly.
BTW, The Parse APP ID and Key is actually directly off the Parse.Com examples and so are probably not genuine keys.
Anil
Hi,
Does anyone in the community has any knowledge on using VFP 9 to access the Parse.Com Restful API?
e.g Here's a CURL script
curl -X POST -H "X-Parse-Application-Id: rEQZDWCoN3MbhOQwSZMMU2MgDKWYp5AQSRlRZJ2H" -H "X-Parse-REST-API-Key: 9pnEkZ93SuZBQfyHRBW735whEwOvUkS3QU1tfoXo" -H...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.