[
https://issues.apache.org/jira/browse/HADOOP-10193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923055#comment-13923055
]
Eugene Koifman commented on HADOOP-10193:
-----------------------------------------
[~tucu00] yes, that will work, but the issue is that some WebHCat aka Templeton
(which uses AuthFilter) clients are sending it as form parameter. Is there a
good way to handle this w/o changing all the clients?
> hadoop-auth's PseudoAuthenticationHandler can consume getInputStream
> --------------------------------------------------------------------
>
> Key: HADOOP-10193
> URL: https://issues.apache.org/jira/browse/HADOOP-10193
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Reporter: Gregory Chanan
> Assignee: Gregory Chanan
> Priority: Minor
> Fix For: 2.3.0
>
> Attachments: HADOOP-10193.patch, HADOOP-10193v2.patch
>
>
> I'm trying to use the AuthenticationFilter in front of Apache Solr. The
> issue I'm running into is that the PseudoAuthenticationHandler calls
> ServletRequest.getParameter which affects future calls to
> ServletRequest.getInputStream. I.e. from the javadoc:
> {code}
> If the parameter data was sent in the request body, such as occurs with an
> HTTP POST request, then reading the body directly via getInputStream() or
> getReader() can interfere with the execution of this method.
> {code}
> Solr calls getInputStream after the filter and errors result.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
