Ready-made static configuration files for autoprovision (ap_configurations)

Overview

Provides access to template files for autoprovisioning.

The directory is located in the category of automatically synchronized directories :SYNC.

During autoprovision service operation, in response to a request for a specific file, the first thing is to check its presence in this directory. And only in case of its absence the private configuration is searched and built on the basis of a template. Firmware, general boot configurations, as well as individual configurations for specific phones or subscribers can be located here.

Requests

HTTP verb Endpoint Description

POST

/rest/v1/fs/targets/ap_configurations

Pouring a group of files

GET

/rest/v1/fs/targets/ap_configurations

Getting a list of files

GET

/rest/v1/fs/targets/ap_configurations/<filename>

File download

PUT

/rest/v1/fs/targets/ap_configurations/<filename>

Reloading an existing file

DELETE

/rest/v1/fs/targets/ap_configurations/<filename>

Deleting a file

HEAD

/rest/v1/fs/targets/ap_configurations/<filename>

Getting meta-information about a file

Pouring a group of files

Uploading to the collection is done by Content-Type: multipart/formdata.

There can be one or more files in the request. The files are placed under the names specified in the Content-Disposition headers of each part.

If a file with the specified name already exists, it is not saved and returns an error. Depending on the Content-Type and the presence of successfully placed files, the request may return a failed HTTP response, or failure information in the body of the HTTP response 200 OK.

Request

Request example
POST /rest/v1/fs/targets/ap_configurations HTTP/1.1
Content-Type: multipart/form-data; boundary=-----------boundary_69df8120352a996e

-----------boundary_69df8120352a996e
Content-Type: application/octet-stream
Content-Disposition: form-data; name="filename"; filename="7d530b24a037.cfg"
Content-Transfer-Encoding: binary

BINARY BODY OF '7d530b24a037.cfg'
-----------boundary_69df8120352a996e--

Response

Response example
[
  {
    "name": "17a2971e85.cfg",
    "size": 2150,
    "status": "ok"
  }
]

Getting a list of files

Request

Table 1. Request parameters
Name Type Description

filter

object

Filter by field values.

mask

str

List of fields to output. Available fields for output: name, size, last_modified.

offset

int

Offset in the list of files to be issued.

limit

int

Maximum number of files in the list.

order

array<object|str>

The sort order of the files in the list.

Details about the format of GET request parameters

Request example
GET /rest/v1/fs/targets/ap_configurations HTTP/1.1

Response

Response example
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8

[
  {
    "name": "17a2971e85.cfg",
    "size": 2150,
    "last_modified": "2022-01-14 03:00:12"
  },
  {
    "name": "17a2971e86.cfg",
    "size": 2183,
    "last_modified": "2022-01-14 03:14:02"
  }
]

File download

Request

Table 2. Request parameters
Name Type Description

attachment

bool

Issuance Type. Default false.

true – is output with the header Content-Disposition: attachment; filename=filename.ext or Content-Disposition: attachment; filename*=UTF-8''%d1%84%d0%b0%d0%b9%d0%bb.ext, where file.ext is the file name in UTF-8 encoding and URLencoded.

false – untitled Content-Disposition.
Request example
GET /rest/v1/fs/targets/ap_configurations/7d530b24a037.cfg?attachment=true HTTP/1.1

Response

Response example
HTTP/1.1 200 OK
Content-Type: application/octet-stream; charset=utf-8
Content-Disposition: attachment; filename*=UTF-8''7d530b24a037.cfg

BINARY BODY OF '7d530b24a037.cfg'

Reloading an existing file

Performs a file replacement.

A single file is uploaded either with Content-Type: multipart/formdata, or with an arbitrary Content-Type that is not multipart.

If the download is done with Content-Type: multipart/formdata, then only the first file will be saved (the first part with the filename field in the header) Content-Disposition), and the file name itself will be ignored.

Request

Request example (octet-stream)
PUT /rest/v1/fs/targets/ap_configurations/7d530b24a037.cfg HTTP/1.1
Content-Type: application/octet-stream

BINARY BODY OF '7d530b24a037.cfg'
Request example (multipart)
PUT /rest/v1/fs/targets/ap_configurations/7d530b24a037.cfg HTTP/1.1
Content-Type: multipart/form-data; boundary=-----------boundary_69df8120352a996e

-----------boundary_69df8120352a996e
Content-Type: application/octet-stream
Content-Disposition: form-data; name="7d530b24a037.cfg"; filename="7d530b24a037.cfg"
Content-Transfer-Encoding: binary

BINARY BODY OF '7d530b24a037.cfg'
-----------boundary_69df8120352a996e--

Response

Response example
HTTP/1.1 204 No Content

Deleting a file

Request

Request example
DELETE /rest/v1/fs/targets/ap_configurations/7d530b24a037.cfg HTTP/1.1

Response

Response example
HTTP/1.1 204 No Content

Getting meta-information about a file

Returns meta-information about the file, including the size in the header Content-Length.

Features

  • HTTP-the response does not contain a body, despite the presence of a header Content-Length.

Request

Table 3. Request parameters
Name Type Description

attachment

bool

Issuance Type. Default false.

true – is output with the header Content-Disposition: attachment; filename=filename.ext or Content-Disposition: attachment; filename*=UTF-8''%d1%84%d0%b0%d0%b9%d0%bb.ext, where file.ext is the file name in UTF-8 encoding and URLencoded.

false – untitled Content-Disposition.
Request example
HEAD /rest/v1/fs/targets/ap_configurations/7d530b24a037.cfg?attachment=true HTTP/1.1

Response

Example of a successful response
HTTP/1.1 200 OK
Content-Type: application/octet-stream
Last-Modified: Fri, 14 Jan 2022 00:00:12 GMT 2022-01-14 03:00:12
Content-Disposition: attachment; filename=17a2971e85.cfg
Content-Length: 2150
Example of an unsuccessful response
HTTP/1.1 404 Not Found

See also

  • Personalization
  • Increase font size
  • Decrease font size