Check BLOB
Checks the existence of a BLOB by its SHA256 digest
- Parameters
- Advanced call ?
Function CheckBlob(Val URL, Val SHA256, Val AdditionalHeaders = "") Export
| Parameter | CLI option | Type | Required | Description |
|---|---|---|---|---|
| URL | --url | String | ✔ | Ollama server URL |
| SHA256 | --digest | String | ✔ | SHA256 BLOB digest |
| AdditionalHeaders | --headers | Map Of KeyAndValue | ✖ | Additional request headers, if necessary |
Returns
Map Of KeyAndValue - Processing result
| Parameter | Description |
|---|---|
| proxy | InternetProxy or a structure with fields Protocol, Host, Port, User, Password, UseOSAuthentication |
| timeout | Request execution timeout |
| adv_response | Formats the response as a complete HTTP structure with fields code, body, and headers |
| retries | Number of HTTP request send attempts on 5** status codes or internal client errors |
| dontwait | Creates a background job and returns its data (for 1C and OneScript only) |
tip
Method at API documentation: Check if a Blob Exists
1C:Enterprise/OneScript code example
URL = "https://hut.openintegrations.dev/ollama";
Token = "12We34..."; // Authorization - not part API Ollama
SHA256 = "988e7924f32c474bb0423055f90c893b0a9aa1e22ad0e6b639df3676b6af1555";
AdditionalHeaders = New Map;
AdditionalHeaders.Insert("Authorization", StrTemplate("Bearer %1", Token));
Result = OPI_Ollama.CheckBlob(URL, SHA256, AdditionalHeaders);
- Bash
- CMD/Bat
# JSON data can also be passed as a path to a .json file
oint ollama CheckBlob \
--url "https://hut.openintegrations.dev/ollama" \
--digest "yoyoyo" \
--headers "{'Authorization':'***'}"
:: JSON data can also be passed as a path to a .json file
oint ollama CheckBlob ^
--url "https://hut.openintegrations.dev/ollama" ^
--digest "yoyoyo" ^
--headers "{'Authorization':'***'}"
Result
{
"status_code": 200
}