Internal error: A ContentConsumer of class "{1}" was selected for the Content-Type "{0}" but it, and no other matching consumers, accepted the message. A ContentConsumer does not support more than one transfer at a time: the consumer of type {0} is already in use. Check whether the implementation of putData is invoking its superclass to terminate the message. Argument {0} must be a nonempty string or character vector. The value of the header field "{0}" must be a scalar. It was a {1} array with values: {2} The character ''{0}'' in "{1}" is not valid in a {2}. The specified function handle to receive data must have at least one output. A {1} must not contain a header field "{0}". A {2} must not contain a field "{0}" with the value "{1}". The value "{2}" (of type {1}) is not valid for a "{0}" header field. The number {0,number,integer} is not an open file identifier. The filename "{0}" is invalid because it contains wildcard characters. The media type "{0}" has an invalid character or syntax. It must be of the form "type/subtype". The name "{0}" is not supported for a header field of type {1}. Choices are: {2} The quality value "{0}" is not a number in the range 0-1. The parameter "{0}" has an invalid character or syntax. It must be of the form "name=value". Warning: The encoding "{0}" in "{1}" is not an acceptable %-encoding in the range 00-FF. The function handle specified for argument {0,number,integer} must have at least one input and two outputs. The PUTHANDLE function must have at least one input and two outputs. Warning: The "Content-Location" field value of "{0}" must have an empty Fragment, not "{1}". Bad protocol version: "{0}". It must be similar to "HTTP/1.1". Warning: The RequestLine "{0}" is inconsistent with the URI {1} and the method "{2}"; expected "{3}". The request may fail or parts of the RequestLine may be ignored. Warning: {0} The request may fail or parts of the RequestLine may be ignored. the return value from the {0} method The RequestTarget "{1}" in the RequestLine "{0}" must be "{2}" for this type of request. The value "{0}" is not a valid URI. Unable to convert data of type {0} to XML. Input must be of the Java type org.w3c.dom.Document, and can be generated by xmlread or com.mathworks.xml.XMLUtils.createDocument. Expected a message using request method {0} to have a Body. Body unexpected in message using request method {0}. A multipart Content-Type message was received without a "boundary" parameter. << {0} bytes of unknown type >> << {0} bytes of {1} data >> MultipartProvder's Parts property must not be changed after transfer has started. An error occurred calling the function "{0}" to obtain a ContentConsumer for Content-Type "{1}". Could not convert data of type {0} with dimensions ({1}) to payload for Content-Type "{2}":\n{3} Unable to convert the value of parameter "{0}" to a scalar string. Unable to convert the value of the query parameter "{0}" of type {1} to a string. Unable to convert header field value "{0}" to a string. An error occurred while trying to convert the payload of the response from {0} using the media-type {1}. The unconverted data may be found in this exceptions's History.Response(end).Body. To disable automatic conversion, set HTTPOptions.ConvertResponse to false. An error occurred while trying to convert the payload of the response using the media type {0}. MATLAB cannot convert audio data to subtype "{0}". Supported subtypes are: {1}. Unable to convert compressed payloads. The encoding is "{0}". The error "{0}" occurred trying to create or overwrite "{1}". The directory may not allow creating files. The file "{0}" exists and an attempt to derive a unique name by appending a number failed because all names from "{0}" to up to "{1}" were used. Unable to determine Content-Type for data of type "{0}" with dimensions ({1}). Specify desired Content-Type HeaderField. Attempted to create the file "{0}", but it already exists, but FileConsumer was created with the filename "{1}". FileConsumer will not overwrite an existing file unless you specify the exact name in the constructor. Alternatively, specify PERMISSION of 'u' or 'u+' to generate a unique name. Attempted to create the file "{0}", but it already exists, and no filename was specified in the FileConsumer constructor. FileConsumer will not overwrite an existing file unless you specify the exact name in the constructor. Alternatively, specify PERMISSION of 'u' or 'u+' to generate a unique name. Could not restore the seek position in order to restart the transfer of the file {0}. The ContentProvider of type "{0}" was already used for a previous message. If your provider can be reused for another message, override the reusable method to return true. Otherwise create a new provider. The ContentConsumer of type "{0}" rejected the message, possibly because of the Content-Type "{1}". The message will be processed in a default manner. The ContentProvider of type "{0}" was already used to send data in a message. If your provider can be restarted for the same message, override the restartable method to return true. Otherwise create a new provider. The PutMethod property can only be set to empty. In {0}: the value is a cell array. Only scalars and char vectors allowed. The header field "{0}" in the message part was expected to contain the value "{1}". A Content-Length field with the value {0} was found in the message, which is inconsistent with chunked transfer coding. Internal error: Unable to find ContentConsumer for Content-Type "{0}". Data of type "{0}" with size ({1}) cannot be converted to or is inconsistent with Content-Type "{2}". the return value of the function "{1}" invoked for Content-Type "{0}" The folder "{0}" does not exist or is not accessible. Cannot create a file in "{0}" because the folder is read-only. Available classes in matlab.net.http.field and names they support: More than one FIELDS parameter specified. Message contains multiple "{0}" fields with different values. The header field with the value "{0}" has an empty name. A multipart message must contain at least one part. The "{0}" value in an AuthInfo is an encoded token that must not appear for the "Digest" scheme and must not be followed by additional parameters. The "Encoded" property of an AuthInfo must be the only other property and cannot be used for the "Digest" Scheme. Error writing to temporary file "{0}". Implementation restriction: Sending an "Expect: 100-continue" header in a request message may cause a hang or timeout waiting for the server to respond with a status other than "100 Continue". Some of the arguments are {0} and some are not. A mixture of argument types is not supported. Unable to convert the value "{2}" (type {1}) for the {0} header field to an integer. The number {0,number,integer} is not an open file identifier. The file identifier {0,number,integer}, which points to "{1}", was not opened for reading. The file identifier {0,number,integer} was not opened for writing. The file "{0}" exists but is not readable. The file "{0}" does not exist or is not readable. The file "{0}" exists but is not writable. The path "{0}" is not writable because it is a folder or read-only file. The date "{0}" for the "Date" field must not be in the future. It is greater than "{1}". The specified GetCredentialsFcn has {0} inputs and {1} outputs; it must have at least {2} inputs and {3} outputs. Warning: The URI "{0}" specified for {1} must have a host name. Illegal character ''{0}'' found in token "{1}". A character with the hex value "{0}" was found in a header field. Values must contain only visible ASCII characters, space or tab. The value "{0}" is not valid for the {1} property of a URI. The value for a date field must be a datetime object, string or character vector, not "{0}". The name "{0}" specified for the {2} object is not one of the supported names: {1} A {1} field named "{3}" is not supported in a header field named "{0}": {2} A {0} header field was found with the value "{1}". It must be "{2}". The value "{2}" (type {1}) for the {0} header field must be a host name optionally followed by a port, for example "foo.com:80". Invalid field name "{0}" in FIELDS argument. REQUEST {0,number,integer} to {1} at {2} - {3} ({4} sec): {5} REQUEST {0,number,integer} to {1} at {2}: {3} RESPONSE {0,number,integer} at {1} - {2} ({3} sec) RESPONSE {0,number,integer} at {1} ***Exception*** The Content-Type "{0}" is not supported for string or character data. Use a uint8 vector. Did you forget to save the all the return values from {0}.{1} (expected {2,number,integer})? Malformed multipart message received from the server. The end boundary marker is missing. Any parts of the message already converted can be found in the Body of the last ResponseMessage in this exception's History. The convert method is not implemented by class {0} or its superclasses in its package. The class will not be automatically used to create header fields. The HTTP request is marked "completed" but is missing a request method such as GET, PUT, etc. The class {0} is missing the static {1} method. The class will not be automatically used to create header fields. Value missing for "{0}". Progress monitor is already in use for another transfer. More than one class implements the header field "{0}": {1} and {2} There is more than one header field with the name "{0}". Objects being compared must be the same class. Unable to convert a HeaderField with an empty name. An attempt was made to create a {0} with the Name "{1}", but this name is reserved for use by {2}. The value of the query parameter "{0}" has a datetime of NaT, which cannot be converted to a query value. The FIELDS array [{0}] does not have unique field names. The nc property value "{0}" in AuthInfo is not a positive hex integer. In {0}: the value of type {1} is not supported because it has no string or char method. Unable to use the convert method for a HeaderField named "{0}" because there is no custom subclass in the matlab.net.http.field package that supports this name. Use <a href="matlab:matlab.net.http.HeaderField.displaySubclasses">HeaderField.displaySubclasses</a> to see the list of custom subclasses. There is no header field with the name "{0}". The {0} handle must have {1,number,integer} return values. Instead, it has {2,number,integer}. None of the meta.class objects passed in are valid classes. The header field "{0}" does not allow values of type {1}: {2} The putData method of {0} was called but the object was not initialized. Check whether the implementation of the initialize method is invoking its superclass. Error in the definition of {0}. Every class in the matlab.net.http.field package must be subclass of matlab.net.http.HeaderField. The class "{0}" is not a subclass of matlab.net.http.HeaderField. The class "{0}" is not a subclass of matlab.net.http.HeaderField or is not in the matlab.net.http.field package. The constructor was called with an odd number of arguments. Initiating another web service request while one is currently in progress is not supported. Warning: One or more parts of the multipart message is malformed: it contains no blank line at the end of the header. The "{0}" header field does not allow a "q" parameter. The structure for an AuthInfo must have a "Scheme" field. The value "{0}" contains the separator "{1}". A value of type {1} is not valid for the field "{0}": {2}. Warning: The character "{0}" in the "{1}" is outside the range of ASCII characters permitted in an encoded string. The string or char function used on the value of query parameter "{0}" of type {1} returned the type {2} instead of a string or character vector. The payload of the message is only {0,number,integer} bytes, but the Content-Length field value is {1,number,integer}. This will likely cause a timeout waiting for a response from the server. The ContentProvider "{0}" sent only {1,number,integer} bytes, but the Content-Length field value is {2,number,integer}. This will likely cause a timeout waiting for a response from the server. The ContentProvider of type "{0}" returned only {1,number,integer} bytes when {2,number,integer} were expected based on the Content-Length field in the request message or the value returned by expectedContentLength. The ContentProvider of type "{0}" returned {1,number,integer} bytes when only {2,number,integer} were expected based on the Content-Length field in the request message or value returned by expectedContentLength. << {0} total characters of data >> << {0} total characters of {1} data >> The StartLine "{0}" contains {1,number,integer} parts. It must have at most 3. Transfer aborted due to exception while transferring or converting data. See the cause property of this exception for more information. Unable to send a message using the scheme "{0}". Only "http" and "https" are supported. The URI "{0}" must specify a host. The header field "{0}" expected a vector, not "{2}" of type {1}. The following error occurred using xmlwrite to convert the data: {0}