title: Jersey and @FormParam not working when charset is specified in the Content-Type
body: <p>It seems like Jersey 2.0 (using servlet 3.1) is not able to decode a parameter when the <code>charset</code> property is specified in the <code>Content-Type</code> header.</p>
  
  <p>For example considering the following endpoint:</p>
  
  <pre><code>@POST
  @Path("/hello")
  @Consumes(MediaType.APPLICATION_FORM_URLENCODED)
  @Produces(MediaType.APPLICATION_JSON)
  public Response hello(@FormParam("name") String name) {
      System.out.println(name);
      return ok();
  }
  </code></pre>
  
  <p>This curl request works:</p>
  
  <pre><code>curl -X POST -H "content-type: application/x-www-form-urlencoded" -d "name=tom" http://localhost:8080/sampleapp/hello
  </code></pre>
  
  <p>The following request instead <strong>doesn't</strong> work and the <code>name</code> parameter is <code>null</code>:</p>
  
  <pre><code>curl -X POST -H "content-type: application/x-www-form-urlencoded; charset=UTF-8" -d "name=tom" http://localhost:8080/sampleapp/hello
  </code></pre>
  
  <p>I think the <code>charset=UTF-8</code> addition in the content type breaks my code. </p>
  
  <p><strong>EDIT:</strong></p>
  
  <p>I've opened an official ticket just in case this is a bug: <a href="https://java.net/jira/browse/JERSEY-1978" rel="noreferrer">https://java.net/jira/browse/JERSEY-1978</a></p>