[
https://issues.apache.org/jira/browse/DRILL-5494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003168#comment-16003168
]
Paul Rogers commented on DRILL-5494:
------------------------------------
Similarly, on a secure system, login using the Drill login page. The following
appears in {{drillbits.out}}:
{code}
May 09, 2017 12:56:56 PM org.glassfish.jersey.servlet.WebComponent
filterFormParameters
WARNING: A servlet request to the URI http://xx.xx.xx.xxx:8047/login contains
form parameters in the request body but the request body has been consumed by
the servlet or a servlet filter accessing the request parameters. Only resource
methods using @FormParam will work as expected. Resource methods consuming the
request body by other means will not work as expected.
{code}
> Badly-formed HTTP handler in web client
> ---------------------------------------
>
> Key: DRILL-5494
> URL: https://issues.apache.org/jira/browse/DRILL-5494
> Project: Apache Drill
> Issue Type: Bug
> Affects Versions: 1.10.0
> Reporter: Paul Rogers
> Priority: Minor
>
> Start Drill 1.10. Look in the {{drillbits.out}} log file. Find this line:
> {code}
> May 01, 2017 4:17:05 PM org.glassfish.jersey.internal.Errors logErrors
> WARNING: The following warnings have been detected: HINT: A HTTP GET method,
> public void
> org.apache.drill.exec.server.rest.LogInLogOutResources.logout(javax.servlet.http.HttpServletRequest,javax.servlet.http.HttpServletResponse)
> throws java.lang.Exception, returns a void type. It can be intentional and
> perfectly fine, but it is a little uncommon that GET method returns always
> "204 No Content".
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
