FYI using global templating instead of the transformers does the same issue...

Looks like a bug to me. Hopefully I'll find a workaround

@Tom what do you think ? 😕

My whole json :

{

"request": {

"method": "GET",

"urlPathPattern": "/myprolink/adc/golden/.*"

},

"response": {

"status": 200,

"bodyFileName": "goldens/C0402.png",

"transformers": ["response-template"],

"headers": {

"Content-Type": "image/png"

}

}

}

obviously we need the file in the correct place for it to fail like above, otherwise we have a clean

HTTP ERROR 500 java.io.FileNotFoundException: /home/wiremock/./__files/goldens/C0402.png (No such file or directory)

Do you need me to enter an issue on a github or something ?

I may not be able to look for a little while as I’m fully tied up today and at a conference all next week, but if I have something I can run and see it fail I might be able to take a look while I’m on the train.

So basicaly, run WireMock in standalone docker as the documentation state :

docker run -it --rm -p 8080:8080 --name wiremock -v #YOURLOCALFOLDER#:/home/wiremock wiremock/wiremock:3.3.1

In your mapping directory, use this simple JSON (also attached)

{

"request": {

"method": "GET",

"urlPathPattern": "/my/path/ok"

},

"response": {

"status": 200,

"bodyFileName": "C0603.png",

"transformers": ["response-template"],

"headers": {

"Content-Type": "image/png"

}

}

}

And the image must be in your __files folder, but I'm sure you know that. Try to access localhost:8080/my/path/ok --> very weird exception. Remove the transformers from the JSON, try to access the same path (after reload of docker of course) --> image is displayed

get-golden.json

note : it happens with all the png's I tried. But for some, it is a browser error, saying the image has error (which do not happen if I remove the transformers)

note : it is not a new issue, this seems related : https://stackoverflow.com/questions/71708345/wiremock-global-response-templating-causing-500-when-returning-certain-media-f

Note : I found a workaround by encoding in base64 then decoding from base64. But my consumer have to adapt to the mock and this is very ugly.

thx you ! 5-star support again