You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@knox.apache.org by "Robert Levas (JIRA)" <ji...@apache.org> on 2019/01/04 23:14:00 UTC

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

Robert Levas created KNOX-1727:
----------------------------------

             Summary: 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
             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&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)