Hi folks,
I'm trying to push some config to a switch running "WC.16.09", using the API "ConfigPayload" service. The API route I'm using is "/rest/v6/system/config/payload".
In general it works fine, but when the content-length of the POST request exceeds 16072 bytes, I'm getting :
reply: 'HTTP/1.1 413 Request Entity Too Large\r
'
header: Server: eHTTP v2.0
header: Connection: close
header: Content-Type: text/html
Is there any known workaround for this?
I was thinking in sending the json payload as chunks of data, but I'm not sure how it's supposed to be encoded or if it's even supported on the server side.
Best,
Guillermo