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
On coreHTTP the following Init functions do not handle the HTTPClient_InitializeRequestHeaders return code, therefore always succeeding, even when it should fail:
This behavior is confusing because those Init functions return success even if HTTPClient_InitializeRequestHeaders cannot write the request headers. Without request headers, Send functions will raise this error:
Parameter check failed: pRequestHeaders->headersLen does not meet minimum the required length. MinimumRequiredLength=16, HeadersLength=0
Expected behavior
The following Init functions should handle the HTTPClient_InitializeRequestHeaders return code, succeeding only when the headers are written:
Call AzureIoTHTTP_RequestSizeInit or AzureIoTHTTP_Init with a header buffer with 10 bytes of size.
It will succeed even though there is not enough space to write the headers.
Relevant log output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Version
1.1.0
Description of the issue
On coreHTTP the following
Init
functions do not handle theHTTPClient_InitializeRequestHeaders
return code, therefore always succeeding, even when it should fail:This behavior is confusing because those
Init
functions return success even ifHTTPClient_InitializeRequestHeaders
cannot write the request headers. Without request headers,Send
functions will raise this error:Expected behavior
The following
Init
functions should handle theHTTPClient_InitializeRequestHeaders
return code, succeeding only when the headers are written:Steps to reproduce the issue
Call
AzureIoTHTTP_RequestSizeInit
orAzureIoTHTTP_Init
with a header buffer with 10 bytes of size.It will succeed even though there is not enough space to write the headers.
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: