Enabling CORS doesn't seem to work

[Kunal Ashar]

Hi,
I've been used wiremock effectively for some time now, and I wanted to enable CORS access to the mocked APIs.

I've tried setting Access-Control-Allow-Origin: * and other headers in the response header, both to no avail.

Here's an example of a mapping that I have:

{

"request": {

"method": "POST",

"urlPattern": "/api/v2/general/login[\\/\\&\\?]*",

"bodyPatterns": [{

"equalToJson": "{\"password\":\"password\",\"username\":\"ku...@ashar.com\"} ",

"jsonCompareMode": "LENIENT",

"ignoreArrayOrder" : true,

"ignoreExtraElements" : true

}]

},

"response": {

"status": 200,

"headers": {

             "Content-Type": "application/json",

"Access-Control-Allow-Origin" : "*",

"Access-Control-Allow-Methods" : "*",

"Access-Control-Allow-Headers": "Accept, Content-Type, Content-Encoding, Server, Transfer-Encoding",

"X-Content-Type-Options" : "nosniff",

"x-frame-options" : "DENY",

"x-xss-protection" : "1; mode=block"

        },

"bodyFileName": "/login_response_kunalashar.json"

}

}

What am I doing wrong here that's causing CORS to not work?

Thanks in advance.

Kunal Ashar

[Larry Presswood]

I have seen a few proposed solutions on the we that look like what you were trying to do.  Anyone how can we fix this?

[Tom Akehurst]

If you're trying to do a CORS POST, the browser will always make an OPTIONS call first. It's this that needs to return the Access-Control-* headers, so I suggest creating an additional stub for this.

[Kunal Ashar]

Since this post was pretty old and no one had responded, I already tried the OPTIONS method (posted here: https://groups.google.com/forum/#!topic/wiremock-user/xsUvCzg5DeM), and it too didn't work.

[P Singh]

Hi,

Any solution found to this?

I too have landed to the same issue .

[Kunal Ashar]

Not really. Try this, though:

{

    "request":

    {

        "method": "POST",

        "urlPattern": "/api/v2/general/someapi[\\/\\&\\?]*",

        "bodyPatterns": [

        {

"equalToJson": "{\"password\":\"password\",\"username\":\"ku...@ashar.com\"} ",

"jsonCompareMode": "LENIENT",

"ignoreArrayOrder" : true,

"ignoreExtraElements" : true

        }]

    },

    "response":

    {

        "status": 200,

        "headers":

        {

            "Content-Type": "application/json",

            "Access-Control-Allow-Origin": "*",

            "Access-Control-Allow-Methods": "GET, POST, OPTIONS, PUT, DELETE",

            "Access-Control-Allow-Credentials": "true",

            "Access-Control-Allow-Headers": "Content-Type, X-customheader1, X-customheader2, Origin, Accept",

            "Access-Control-Expose-Headers": "Content-Type, X-customheader1, X-customheader2, Origin, Accept"

        },

        "bodyFileName": "/response.json"

[Richie Loco]

I got around this by writing an extension class.  I also needed to create a mapping file expecting request method of OPTIONS. The class I then invoke with Wiremock standalone. 

[Richie Loco]

Following on from my last reply (apologies that it was brief, I am swamped at work).  Please see https://github.com/RichieLoco/WiremockCorsExtension