You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Dilli Arumugam (JIRA)" <ji...@apache.org> on 2013/10/01 18:45:34 UTC
[jira] [Updated] (KNOX-174) support service specific cap for
buffering request entities for replay against WWW-authenticate challenge
[ https://issues.apache.org/jira/browse/KNOX-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dilli Arumugam updated KNOX-174:
--------------------------------
Affects Version/s: 0.3.0
Fix Version/s: 0.4.0
> support service specific cap for buffering request entities for replay against WWW-authenticate challenge
> ---------------------------------------------------------------------------------------------------------
>
> Key: KNOX-174
> URL: https://issues.apache.org/jira/browse/KNOX-174
> Project: Apache Knox
> Issue Type: Improvement
> Affects Versions: 0.3.0
> Reporter: Dilli Arumugam
> Assignee: Dilli Arumugam
> Fix For: 0.4.0
>
>
> We are buffering the request entities for replaying against potential WWW-Authenticate challenge from secure hadoop service.
> We should give a configuration for customers for each hadoop service to cap the buffer size per request. This is also required to protect against denial of service attacks.
--
This message was sent by Atlassian JIRA
(v6.1#6144)