Unexpected response from incomplete url

[mingard]

When there is a notFound image set and an incomplete url e.g. /path/to/image rather than /path/to/image/foo.jpg, a text/html response is returned but with the body of the notFound image.

The expected response would be the same JSON formatted message expected when notFound is not set.

Tested with:

 "notFound": {
    "statusCode": 410,
    "images": {
      "enabled": true,
      "path": "./images/missing.png"
    }
  }

[jimlambie]

@mingard which storage handler is this using? disk or remote?

[mingard]

Remote: S3. Fallback is local.

[jimlambie]

Closed via 55754dc