[
https://issues.apache.org/jira/browse/KNOX-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13782487#comment-13782487
]
ASF subversion and git services commented on KNOX-173:
------------------------------------------------------
Commit 832e86c86e0a82b93fa651f926f3bf76a43cdead in branch refs/heads/master
from [~darumugam]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-knox.git;h=832e86c ]
KNOX-173, leverage presence of delegation token to avoid buffering request
entity
> leverage presence of delegation token to avoid buffering request entity
> ------------------------------------------------------------------------
>
> Key: KNOX-173
> URL: https://issues.apache.org/jira/browse/KNOX-173
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Affects Versions: 0.3.0
> Reporter: Dilli Arumugam
> Assignee: Dilli Arumugam
> Fix For: 0.3.0
>
> Attachments: KNOX-173.patch
>
>
> At present, HttpClientDispatch caches request entities while talking to
> services in secure cluster to replay the entity for a potential
> WWW-Authenticate challenge from service.
> This could be improved by leveraging delegation token coming down with the
> request to Knox. When we pass down the delegation token, we do not expect to
> see WWW-Authenticate challenge. When Knox gets request from client targeted
> to DataNode, it would always have DelegationToken. So, large files would be
> streamed straight without any buffering.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
