Fix "Content-Type" validation

[dlwr]

Hello, I found the issue about "Content-Type" validation and fix it.

Here is sample. I wrote JSON Schema like this,

{
  "title": "Material",
  "definitions": {
    "someDefinitions": "someDefinitions"
  },
  "description": "Material",
  "links" : [
    {
      "description" : "Create Material",
      "href" : "/api/v1/materials",
      "method" : "POST",
      "rel" : "self",
      "encType" : "multipart/*"
    }
  ],
  "properties": {
    "someProperties": "someProperties"
  }
}

then, made request like this,

POST /api/v1/materials HTTP/1.1
Host: localhost:3000
Content-Type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZu0gW

----WebKitFormBoundary7MA4YWxkTrZu0gW
Content-Disposition: form-data; name="texture"; filename="sample_texture.jpg"
Content-Type: image/jpeg


----WebKitFormBoundary7MA4YWxkTrZu0gW
Content-Disposition: form-data; name="title"

sample_title
----WebKitFormBoundary7MA4YWxkTrZu0gW

then, I received error message like this

{
  "error": {
    "status": 400,
    "message": "\"Content-Type\" request header must be set to \"multipart/*\"."
  }
}

This problem was caused by arguments order, they are used by Committee::RequestValidator for call Rack::Mime.match? .

[dlwr]

arguments used conversely here.

this is definition of Rack::Mime.match?
https://github.com/rack/rack/blob/7c574e2593922005ee7993c6aca93aa0383cd973/lib/rack/mime.rb#L28

first argument is expected to value, second is expected to matcher

[brandur]

Hah, that's embarassing. Thank-you @dlwr!

[brandur]

Fix pushed in version 1.6.3.

[dlwr]

THX!