You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Full Replication: export VM as XVA and stream into the import
Incremental Replication: export VDI as VHD and stream into the import
I believe in both exports, XAPI do not provide a content-length header but XAPI doesn't not support chunk encoding either so a content-length header msut be provided by XO.
Or this results in:
<html><body><h1>HTTP 500 internal server error</h1>An unexpected error occurred; please wait a while and try again. If the problem persists, please contact your support representative.<h1> Additional information </h1>IMPORT_ERROR_CANNOT_HANDLE_CHUNKED: [ ]</body></html>
Would it be possible for either having the content length info when doing the export or to implement chunk encoding support so that XO doesn't have to specify the length header?
The text was updated successfully, but these errors were encountered:
For some XO feature:
I believe in both exports, XAPI do not provide a
content-length
header but XAPI doesn't not support chunk encoding either so acontent-length
header msut be provided by XO.Or this results in:
Would it be possible for either having the content length info when doing the export or to implement chunk encoding support so that XO doesn't have to specify the length header?
The text was updated successfully, but these errors were encountered: