Epson TM-m30II Technical Reference Guide TM-m30II-H - Page 120

Request, Response, Table 9 Response Header, Table 10 Response, Function, POST Parameters, Results

Get Epson TM-m30II PDF manuals and user guides View all Epson TM-m30II manuals
Add to My Manuals
Save this manual to your list of manuals

Page 120 highlights

Appendix 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 (when type=static only) X-RateLimit-Reset: 1390941626 (when type=static only) WWW-Authenticate: Digest realm="", nonce="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", qop="auth" Table 10 Response Function Updating the configuration script in volatile memory Deletes the configuration script from volatile memory POST Parameters Results Response { "type" : "volatile", "description": "" } Update successful Update failed 200 OK 413 Request Entity Too Large When the parameter is too long Update failed 500 Internal Server Error When an error occurs when applying a new configuration script { "type" : "volatile", "description": "delete" } Deleting successful Deleting failed 200 OK 500 Internal Server Error 120

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
120
Appendix
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
See the POST parameters in Table 10 Response for the parameters.
Response
Table 9 Response Header
Table 10 Response
Content-Type: text/json; charset=utf-8
http://(printer IP address)/webconfig/beacon.cgi
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
(when type=static only)
X-RateLimit-Reset: 1390941626
(when type=static only)
WWW-Authenticate: Digest realm="<IPaddr>", nonce="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", qop="auth"
Function
POST Parameters
Results
Response
Updating the configuration
script in volatile memory
{
“type” : “volatile”,
“description”: “<The
string for the
configuration script that
performed escape
processing>”
}
Update successful
200 OK
Update failed
When the parameter is too
long
413 Request Entity Too Large
Update failed
When an error occurs
when applying a new
configuration script
500 Internal Server Error
Deletes the configuration
script from volatile memory
{
“type” : “volatile”,
“description”: “delete”
}
Deleting successful
200 OK
Deleting failed
500 Internal Server Error