Mule
  1. Mule
  2. MULE-4999

HttpRequestBodyToParamMap should transform GET method

    Details

    • User impact:
      Medium
    • Similar Issues:
      MULE-4862The HttpRequestBodyToParamMap transformer does not allow for encoded = (equals) character in GET request
      MULE-6098Bug in HttpRequestBodyToParamMap
      MULE-4644HttpRequestBodyToParamMap is too strict when checking for content type
      MULE-4700HttpRequestBodyToParamMap - Allow multi-valued parameters to be transformed
      MULE-4911HttpRequestBodyToParamMap decodes a query string without specifying an encoding.
      MULE-7224body-to-parameter-map-transformer only works with GET and POST
      MULE-7681Revamp transformers
      MULE-4393Message Property Transformer Not Invoked
      MULE-536Inbound Transformers do NOT get invoked if anUMO component implements Callable.
      MULE-3968The JdbcMessageReceiver processMessage method gets database connections unnecessarily

      Description

      In org.mule.transport.http.transformers.HttpRequestBodyToParamMap, method public Object transform(MuleMessage message, String encoding), following code seems to be invalid:
      boolean isUrlEncoded = contentType.startsWith("application/x-www-form-urlencoded");
      It throws Null Exception when invoked with GET HTTP method.
      Suggested change:
      boolean isUrlEncoded = (contentType!=null)? contentType.startsWith("application/x-www-form-urlencoded") : false;

        Activity

        Show
        Dirk Olmes added a comment - 3.x: http://fisheye.codehaus.org/changelog/mule/?cs=18898

          People

          • Assignee:
            Dirk Olmes
            Reporter:
            Łukasz Kolek
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development