topic Re: Upload to cloud works, but fails on local server in API / CLI Discussion

Upload to cloud works, but fails on local server

Christof_Marte — Tue, 26 Sep 2017 09:48:05 GMT

Hi there,

I am trying to communicate with the Thread Prevention API using a C# client. Got a test API key for the cloud, but in the end, I want to use our local system. On the cloud everythin works fine. But on the local system, the upload fails: code:1008,label:BAD_REQUEST, message: Invalid Multipart/form request. I compared the requests using fiddler, they seem to be the same. Something like

POST https://te.checkpoint.com/tecloud/api/v1/file/upload HTTP/1.1
Authorization: TE_API_KEY_n7xxxxxxxxxxxxxxxxxxxxxxxxxxxuP
Content-Type: multipart/form-data; boundary="Upload----09/26/2017 10:31:22"
Host: te.checkpoint.com
Cookie: te_cookie=AOPHKIXA
Content-Length: 23060
Expect: 100-continue

--Upload----09/26/2017 10:31:22
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name=request

{"request":{"extraction":{"scrubbed_parts_codes":null,"method":null},"file_type":"pdf","file_name":"Test.pdf","te":{"images":null,"reports":[]},"features":["te"],"sha1":"314e2eda1b4d26c060ec49c0db11ce1eefc8ee55"}}
--Upload----09/26/2017 10:31:22
Content-Disposition: form-data; name=file; filename=Test.pdf; filename*=utf-8''Test.pdf

%PDF-1.5 .......

The C# upload code sniplet looks like this:

using (var formData = new MultipartFormDataContent("Upload----1234567457645"))
{
formData.Add(stringContent, "request");
formData.Add(fileStreamContent, "file");
var response = client.PostAsync(new Uri(TE_API_URL + UPLOAD_PATH), formData).Result;
if (response.IsSuccessStatusCode)
{
return await response.Content.ReadAsStringAsync();
}
}
return null;

Does anybody have an idea what is going wrong locally?

Re: Upload to cloud works, but fails on local server

PhoneBoy — Tue, 26 Sep 2017 15:43:12 GMT

Moving this to the SandBlast API‌ space and tagging Matan Mishan‌

Can you show the exact API call (and response) you received when you queried the local appliance?

(Obscure the API key, of course)

We do have the SandBlast API documentation‌ that might also be helpful as well.

Re: Upload to cloud works, but fails on local server

Christof_Marte — Wed, 27 Sep 2017 06:54:23 GMT

Hello Dameon,

thank you for your help. These are the local appliance calls:

First, a request to check if the file exists (in this case, I use the eicar test string):

POST https://xx.x.x.xxx:18194/tecloud/api/v1/file/query HTTP/1.1
Content-Type: application/json; charset=utf-8
Host: 10.1.0.239:18194
Content-Length: 215
Expect: 100-continue
Connection: Keep-Alive
{"request":{"extraction":{"scrubbed_parts_codes":null,"method":null},"file_type":"type","file_name":"EICAR.txt","te":{"images":null,"reports":[]},"features":["te"],"sha1":"3395856ce81f2b7382dee72602f798b642f14140"}}

The response is as expected, and it shows that the communication with the local appliance works

HTTP/1.0 200 OK
Date: Wed, 27 Sep 2017 06:32:28 GMT
Server: Check Point SVN foundation
Content-Type: text/html
X-UA-Compatible: IE=EmulateIE7
Connection: Keep-Alive
X-Frame-Options: SAMEORIGIN
Content-Length: 1093
{
"response" : {
"features" : [ "te" ],
"file_name" : "EICAR.txt",
"file_type" : "type",
"md5" : "",
"sha1" : "3395856ce81f2b7382dee72602f798b642f14140",
"sha256" : "",
"status" : {
"code" : 1004,
"label" : "NOT_FOUND",
"message" : "Couldn't find the requested file, please upload it"
},
"te" : {
"images" : [
{
"id" : "5e5de275-a103-4f67-b55b-47532918fa59",
"report" : {
"verdict" : "unknown"
},
"revision" : 1,
"status" : "not_found"
},
{
"id" : "e50e99f3-5963-4573-af9e-e3f4750b55e2",
"report" : {
"verdict" : "unknown"
},
"revision" : 1,
"status" : "not_found"
}
],
"status" : {
"code" : 1004,
"label" : "NOT_FOUND",
"message" : "Couldn't find the requested file, please upload it"
}
}
}
}

The file is not known to the application, so I try to upload:

POST https://xx.x.x.xxx:18194/tecloud/api/v1/file/upload HTTP/1.1
Content-Type: multipart/form-data; boundary="Upload----1234567457645"
Host: 10.1.0.239:18194
Content-Length: 503
Expect: 100-continue
Connection: Keep-Alive
--Upload----1234567457645
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name=request
{"request":{"extraction":{"scrubbed_parts_codes":null,"method":null},"file_type":"pdf","file_name":"EICAR.txt","te":{"images":null,"reports":null},"features":null,"sha1":"3395856ce81f2b7382dee72602f798b642f14140"}}
--Upload----1234567457645
Content-Disposition: form-data; name=file
X5O!P%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*
--Upload----1234567457645--

This upload request uses the multipart-format and is generated by the C# code shown in the question. The response gives an error:

HTTP/1.0 200 OK
Date: Wed, 27 Sep 2017 06:32:30 GMT
Server: Check Point SVN foundation
Content-Type: text/html
X-UA-Compatible: IE=EmulateIE7
Connection: Keep-Alive
X-Frame-Options: SAMEORIGIN
Content-Length: 197
{
"response" : [
{
"status" : {
"code" : 1008,
"label" : "BAD_REQUEST",
"message" : "Invalid Multipart/form request"
}
}
]
}

Using the cloud host te.checkpoint.com, the upload works. There the results are "UPLOAD_SUCCESS". The only difference I see in the cloud (besides using the API key there, of course) is the te_cookie used in the session there.

Re: Upload to cloud works, but fails on local server

Javier_Padilla — Sun, 01 Oct 2017 04:04:45 GMT

Hello Christof, if you are using the same routine for doing the request for both cloud and local apliance then you might be sending the te_cookie to the local appliance, this causes an error because TP API does not provide a cookie therefore it will not understand why you are sending it. If you want to use the same routine, add a load balancer in the middle and insert te_cookie, you can choose whatever you want as a cookie, you will need to do this if you want an application to send files to a Private Cloud ( and mantain persistency ) and not just to a single appliance. So try removing the cookie and also the Authorization Headers, you don't need them for local emulation.