Custom .NET Core Middleware | Dataford Interview Questions

Design a custom .NET Core middleware.

Asked in the Round 1 HackerRank stage. Implement the middleware behavior as a pure function for grading.

Contract

Given a request and simulated downstream result, return a response. Preserve an existing X-Correlation-ID header or use generated when it is absent. Requests whose path starts with /api/ require a non-empty Authorization header and otherwise return status 401 without using the downstream result. If downstream processing fails, return status 500. Otherwise, pass through the downstream status and body while including the correlation ID.

Constraints

request is a dictionary containing a string path and optional headers.
Header names are case-sensitive for this exercise.
API routes are exactly paths beginning with /api/.
downstream contains integer status, string body, and boolean error fields.
The middleware must not use the downstream result for unauthorized API requests.

Function Signature

def custom_middleware(request, downstream):

Your question is Custom .NET Core Middleware. Start with the requirements in the Question tab.

Run and submit as often as you like. When you're ready, talk me through your approach or go straight to the code.

Problem