You are not logged in.
Pages: 1
when TSQLite3HttpClient(Client).CallBackGetResult was called,httpserver got the aParams value using "GET" methord with "url",
is it able to use post instead of get methord,so httpserver gets the aParams value using "POST" methord with "incontent"?
sometimes the length limit is a problem.
Offline
In the current implementation, you can use CallBacks methods with GET and PUT (with ModelRoot/MethodName URI).
POST is reserved for interface-based services.
So if you use PUT, you can sent the HTTP body directly from the client into the server, with no size limit (except the HTTP server itself).
Offline
thanks,i got it.
Offline
Would you change the code of function "TSQLRestClientURI.CallBackPut" in SQLite3Commons.pas:
from:
...
result := URI(Model.getURICallBack(aMethodName,aTable,aID),
'PUT',nil,aResponseHead,@aSentData).Lo;
...
to:
...
result := URI(Model.getURICallBack(aMethodName,aTable,aID),
'PUT',@aResponse,aResponseHead,@aSentData).Lo;
...
so as i can get aParams.Resp when i use CallBackPut.
Offline
TSQLRestClientURI.CallBackPut() will now return any HTTP response content (even if it is not HTTP/1.1 compliant, and not work over some networks).
Offline
many thanks.
Offline
Pages: 1