[jira] [Commented] (KNOX-1727) Values should not be forced in query parameters when proxying through Knox

[Kevin Risden (JIRA)]

    [ 
https://issues.apache.org/jira/browse/KNOX-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16736163#comment-16736163
 ] 

Kevin Risden commented on KNOX-1727:
------------------------------------

Updated patch which passes that test. Need to run all tests again. The manual 
parsing and rebuilding of the query string by HttpUtils and 
IdentityAsserterHttpServletRequestWrapper is very fragile. KNOX-1675 addresses 
this to use the HttpClient stuff instead. 

> Values should not be forced in query parameters when proxying through Knox
> --------------------------------------------------------------------------
>
>                 Key: KNOX-1727
>                 URL: https://issues.apache.org/jira/browse/KNOX-1727
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: Server
>            Reporter: Robert Levas
>            Assignee: Kevin Risden
>            Priority: Major
>             Fix For: 1.3.0
>
>         Attachments: KNOX-1727.patch, KNOX-1727.patch
>
>
> Values should not be forced in query parameters when proxying through Knox.  
> For example if the following query is received by Knox to be forwarded:
> {noformat}
> GET /some_topology/some_service/some_path?param1=value1&param2&param3=value3
> {noformat}
> Knox should not force all query parameters to have (empty) values, like 
> {noformat}
> GET /some_topology/some_service/some_path?param1=value1&param2=&param3=value3
> {noformat}
> Notice {{param2}} vs {{param2=}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)