Tapestry
  1. Tapestry
  2. TAPESTRY-340

url-encoded parameters are not considered in multipart-requests

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 4.0, 3.0.5
    • Fix Version/s: 4.1.3
    • Component/s: Framework
    • Labels:
      None
    • Environment:
      all

      Description

      Problem-setup:
      a component uses URL-encoded parameters inside a form leading to a multipart/mime-encoded request.

      Problem: all these parameters will be ignored (they're expected as parts of the multipart-request).

      Proposed fix:
      In the class org.apache.tapestry.request.RequestContext, replace the method getParameter()
      with the following;
      _________________________________
      public String getParameter(String name)

      { String result = _request.getParameter(name); if ( result != null ) return result; IMultipartDecoder decoder = getDecoder(); if (decoder != null) return decoder.getString(_request, name); return null; }

      ________________________________________

      Apply analogous patch to the method getParameters(String) in the same class.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Marcus Schulte
            Reporter:
            Marcus Schulte
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development