You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Kevin Risden (JIRA)" <ji...@apache.org> on 2019/01/07 15:15:00 UTC
[jira] [Work started] (KNOX-1727) Values should not be forced in
query parameters when proxying through Knox
[ https://issues.apache.org/jira/browse/KNOX-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on KNOX-1727 started by Kevin Risden.
------------------------------------------
> 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
>
>
> 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¶m2¶m3=value3
> {noformat}
> Knox should not force all query parameters to have (empty) values, like
> {noformat}
> GET /some_topology/some_service/some_path?param1=value1¶m2=¶m3=value3
> {noformat}
> Notice {{param2}} vs {{param2=}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)