Table of Contents
Advertisement
When changing using a low frequency less than once an hour, you can save to non-volatile memory; however,
when changing at a higher frequency, you need to save to volatile memory.
When the change is successful, the advertising data is changed.
Request
Content-Type: text/json; charset=utf-8
http://(printer IP address)/webconfig/beacon.cgi
See the POST parameters in Table 10 Response for the parameters.
Response
Table 9 Response Header
Content-Type: application/json; charset=utf-8
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: POST, GET, OPTIONS, HEADER
Access-Control-Allow-Headers: Content-Type, Content-Length, Authorization
X-Content-Type-Options: nosniff
X-XSS-protection: 1; mode=block
X-Frame-Options: deny
Content-Security-Policy: default-src 'none'
X-RateLimit-Limit: 1
(when type=static only)
X-RateLimit-Remaining: 1 or 0
X-RateLimit-Reset: 1390941626
WWW-Authenticate: Digest realm="<IPaddr>", nonce="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", qop="auth"
Table 10 Response
Function
Updating the configuration
script in volatile memory
Deletes the configuration
script from volatile memory
(when type=static only)
(when type=static only)
POST Parameters
{
Update successful
"type" : "volatile",
Update failed
"description": "<The
string for the
When the parameter is too
configuration script that
long
performed escape
processing>"
Update failed
}
When an error occurs
when applying a new
configuration script
{
Deleting successful
"type" : "volatile",
Deleting failed
"description": "delete"
}
Results
200 OK
413 Request Entity Too Large
500 Internal Server Error
200 OK
500 Internal Server Error
Appendix
Response
120
Advertisement
Table of Contents
