Troubleshooting Wolverine.HTTP binding and responses New in 1.14.0
Diagnose Wolverine.HTTP failures at startup and at runtime: the MapWolverineEndpoints refusals ('mapped to GET ... but declares a request body', NoContentIfMissing rules, 'Unable to find a route argument', AsParameters, JSON strategy and Newtonsoft wiring, 'Failed to resolve the generated handler type', F# and ApiVersion refusals), WolverineRequiredException, and runtime responses that are the only symptom: 415 and 406, 400 'Invalid JSON format', 500 'Request body could not be deserialized', 499 on an aborted upload, unparseable query values binding defaults, 400 'Validation failed', the tenant 400, 404 for a missing entity, and 'No HTTP transport client is registered'.
Use when a Wolverine.HTTP app will not start, an endpoint returns a status you did not write, or a GET answers 404 to everything.
Skill details
- Skill name:
wolverine-troubleshooting-http - Applies to:
wolverine - Tags:
troubleshooting,http,wolverine-http,binding,AsParameters,FromBody,FromQuery,NotBody,ProblemDetails,RejectUnparseableQueryValues,WolverineRequiredException,api-versioning,json - Added in: 1.14.0
- License: Proprietary. Copyright JasperFx Software LLC.