You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that https server metadata such as key , cert ,mutualAuth, etc. Are already returned because server.metadata is already added to the result. It's just that allowCORS is missing.
Log contents in mb.log when running mb --loglevel debug
warn: [mb:2525] Running with --allowInjection set. See http://localhost:2525/docs/security for security info
info: [mb:2525] mountebank v2.9.1 now taking orders - point your browser to http://localhost:2525/ for help
debug: [mb:2525] config: {"options":{"allow-injection":true,"allowInjection":true,"local-only":true,"localOnly":true,"port":2525,"noParse":false,"no-parse":false,"formatter":"mountebank-formatters","pidfile":"mb.pid","ipWhitelist":["*"],"ip-whitelist":"*","mock":false,"debug":false,"protofile":"protocols.json","origin":false,"apikey":null,"log":{"level":"debug","transports":{"console":{"colorize":true,"format":"%level: %message"},"file":{"path":"mb.log","format":"json"}}}},"process":{"nodeVersion":"v16.20.2","architecture":"arm64","platform":"darwin"}}
info: [mb:2525] PUT /imposters
debug: [mb:2525] ::ffff:127.0.0.1:50003 => {"imposters":[{"port":1234,"protocol":"http","allowCORS":true}]}
info: [http:1234] Open for business...
info: [mb:2525] GET /imposters?replayable=true&removeProxies=false```
The text was updated successfully, but these errors were encountered:
Expected behaviour
allowCORS: true
replayable: true
allowCORS: true
Note that https server metadata such as
key
,cert
,mutualAuth
, etc. Are already returned becauseserver.metadata
is already added to the result. It's just thatallowCORS
is missing.Actual behaviour
allowCORS
field is missingSteps to reproduce
PUT http://localhost:2525/imposters
GET http://localhost:2525/imposters
Expected would be :
Software versions used
Log contents in mb.log when running mb --loglevel debug
The text was updated successfully, but these errors were encountered: