text/microsoft-resx 2.0 System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 The stream does not support concurrent read operations. The content length of the request content can't be determined. Either set TransferEncodingChunked to true, load content into buffer, or set MaxRequestContentBufferSize. The libcurl library in use ({0}) does not support different credentials for different authentication schemes. New-line characters in header values must be followed by a white-space character. The stream does not support writing. An error occurred while sending the request. The reason phrase must not contain new-line characters. Response status code does not indicate success: {0} ({1}). Cannot write more bytes to the buffer than the configured maximum buffer size: {0}. The handler does not support client authentication certificates with this combination of libcurl ({0}) and its SSL backend ("{1}"). Cannot add value because header '{0}' does not support multiple values. Value for header '{0}' contains invalid new-line characters. Value: '{1}'. Value '{0}' is not a valid email address. Error: {1} The 'q' value is invalid: '{0}'. An invalid request URI was provided. The request URI must either be an absolute URI or BaseAddress must be set. The server returned an invalid or unrecognized response. An invalid character was found in header name. When using CookieUsePolicy.UseSpecifiedCookieContainer, the CookieContainer property must not be null. Only 'http' and 'https' schemes are allowed. Stream does not support writing. A request message must be provided. It cannot be null. The specified value must be greater than {0}. The specified value is not a valid 'From' header string. The process cannot access the file because it is being used by another process. Unable to read data from the transport connection. The connection was closed before all data could be read. Expected {0} bytes, read {1} bytes. An invalid character was found in the mail header: '{0}'. The character set provided in ContentType is invalid. Cannot read content as string using an invalid character set. Misused header name. Make sure request headers are used with HttpRequestMessage, response headers with HttpResponseMessage, and content headers with HttpContent objects. Using this feature requires Windows 10 Version 1607. The handler does not support custom handling of certificates with this combination of libcurl ({0}) and its SSL backend ("{1}"). Could not find a part of the path '{0}'. The username for a credential object cannot be null or empty. The buffer was not long enough. The async operation did not return a System.Threading.Tasks.Task object. The stream does not support concurrent I/O read or write operations. When using a non-null Proxy, the WindowsProxyUsePolicy property must be set to WindowsProxyUsePolicy.UseCustomProxy. Unable to find the specified file. Specified file length was too large for the file system. The specified file name or path is too long, or a component of the specified path is too long. Client certificate was not found in the personal (\"MY\") certificate store. In UWP, client certificates are only supported if they have been added to that certificate store. Error while copying content to a stream. Handler did not return a response message. The specified string is not in the form required for an e-mail address. Access to the path is denied. The process cannot access the file '{0}' because it is being used by another process. The write operation failed, see inner exception. 'Transfer-Encoding: chunked' header can not be used when content object is not specified. The number of elements is greater than the available space from arrayIndex to the end of the destination array. The read operation failed, see inner exception. The field cannot be longer than {0} characters. Access to the path '{0}' is denied. The {0} property must be set to '{1}' to use this property. The HTTP response headers length exceeded the set limit of {0} bytes. The handler does not support changing revocation settings with this combination of libcurl ({0}) and its SSL backend ("{1}"). The value '{0}' is not supported for property '{1}'. This instance has already started one or more requests. Properties can only be modified before sending the first request. The '{0}'='{1}' part of the cookie is invalid. Could not find a part of the path. The libcurl library in use ({0}) does not support HTTPS. The header name format is invalid. The base address must be an absolute URI. The request message was already sent. Cannot send the same request message multiple times. When using WindowsProxyUsePolicy.UseCustomProxy, the Proxy property must not be null. Buffering more than {0} bytes is not supported. Can not access a closed Stream. The format of value '{0}' is invalid. Invalid range. At least one of the two parameters must not be null. The file '{0}' already exists. Stream does not support reading. The handler was disposed of while active operations were in progress. Value '{0}' is not a valid Base64 string. Error: {1} The inner handler has not been assigned. The specified value is not a valid quoted string. The requested security protocol is not supported. The specified value is not a valid 'Host' header string. The value cannot be null or empty. Positive number required. The mail header is malformed. Could not find file '{0}'. The given header was not found. The format of the HTTP method is invalid. The stream was already consumed. It cannot be read again.