[
https://issues.apache.org/jira/browse/HTTPCLIENT-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973421#comment-14973421
]
Oleg Kalnichevski edited comment on HTTPCLIENT-1693 at 10/25/15 8:24 PM:
-------------------------------------------------------------------------
Daneel,
(1) In my opinion trailers conceptually belong to the entity enclosed in HTTP
message, and not the message itself. Therefore from the API standpoint I would
very much rather prefer trailers to be exposed by HttpEntity than HttpMessage.
(2) Both blocking and non-blocking transports should handle message trailers
consistently.
(3) This is a terrible way to handle exceptions
{code:java}
try {
...
} catch (Exception e) {
throw new IOException(e);
}
{code}
Oleg
was (Author: olegk):
Daneel,
(1) In my opinion trailers conceptually belong to the entity enclosed in HTTP
message, and not the message itself. Therefore from the API standpoint I would
very much rather prefer trailers to be exposed by HttpEntity rather than
HttpMessage.
(2) Both blocking and non-blocking transports should handle message trailers
consistently.
(3) This is a terrible way to handle exceptions
{code:java}
try {
...
} catch (Exception e) {
throw new IOException(e);
}
{code}
Oleg
> Send HTTP trailers in request
> -----------------------------
>
> Key: HTTPCLIENT-1693
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1693
> Project: HttpComponents HttpClient
> Issue Type: New Feature
> Components: HttpClient
> Reporter: Daneel Yaitskov
>
> Currently HTTP client doesn't support sending trailers to a web server.
> The section https://tools.ietf.org/html/rfc7230#section-4.4 is need to be
> implemented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
