Added support for Multipart blueprint specifications

[subinvarghesein]

For request containing multipart form data, browsers provide dynamic form boundary values (like WebKitFormBoundaryjy0tIlk46ESOni0H) which in turn change the content type (to something like multipart/form-data; boundary=---WebKitFormBoundaryjy0tIlk46ESOni0H)

Moreover, request body also can be different because of form boundary.

Sample Request body:

    ------WebKitFormBoundaryjy0tIlk46ESOni0H
    Content-Disposition: form-data; name="documentImportId"

    undefined
    ------WebKitFormBoundaryjy0tIlk46ESOni0H
    Content-Disposition: form-data; name="qquuid"

    e3a2d2ed-0554-42c2-9629-3fad804547d8
    ------WebKitFormBoundaryjy0tIlk46ESOni0H
    Content-Disposition: form-data; name="qqfilename"

    tmprp8v07
    ------WebKitFormBoundaryjy0tIlk46ESOni0H
    Content-Disposition: form-data; name="qqtotalfilesize"

    -1
    ------WebKitFormBoundaryjy0tIlk46ESOni0H
    Content-Disposition: form-data; name="qqfile"; filename="tmprp8v07"
    Content-Type: application/octet-stream

    ------WebKitFormBoundaryjy0tIlk46ESOni0H--

This patch supports this behavior. If content types provided in the request and in spec are both "multipart/form-data" then request body check is not performed and the relevant response provided in the spec is served.

Todo:

• Check how to serve different responses based on the request body if content type is multipart/form-data in both cases

[yakovkhalinsky]

Merging