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
Describe the bug
As per erlang documentation on httpc:request options:
full_result - Defines if a "full result" is to be returned to the caller (that is, the body, the headers, and the entire status line) or not (the body and the status code).
Default is true.
It it not specified that it does not apply if the request is async. The logical conclusion is that it applies to both.
Expected behavior
Both request should have a result of the type {StatusCode, HttpBodyResult}
However, first request has a result of the type {StatusCode, HttpBodyResult} but second request (async) has a result of the type {StatusLine, [HttpHeader], HttpBodyResult}
Either the return of async request should be {StatusCode, HttpBodyResult} or the documentation should be clarified.
Affected versions
Latest
The text was updated successfully, but these errors were encountered:
Xavier59
changed the title
httpc:request full_result options does not work in async mode
httpc:request full_result option does not work in async mode
May 31, 2024
Describe the bug
As per erlang documentation on httpc:request options:
It it not specified that it does not apply if the request is async. The logical conclusion is that it applies to both.
To Reproduce
Steps to reproduce the behavior.
Expected behavior
Both request should have a result of the type
{StatusCode, HttpBodyResult}
However, first request has a result of the type
{StatusCode, HttpBodyResult}
but second request (async) has a result of the type{StatusLine, [HttpHeader], HttpBodyResult}
Either the return of async request should be
{StatusCode, HttpBodyResult}
or the documentation should be clarified.Affected versions
Latest
The text was updated successfully, but these errors were encountered: