How do you add custom response headers or set cookies inside an exception filter in NestJS?

Q: How do you add custom response headers or set cookies inside an exception filter in NestJS?

@Catch(HttpException) export class HttpExceptionFilter implements ExceptionFilter { catch(exception: HttpException, host: ArgumentsHost): void { const ctx = host.switchToHttp(); const res = ctx.getResponse (); // Express Response const req = ctx.getRequest (); const status = exception.getStatus(); // Add custom headers res.setHeader('X-Error-Code', `ERR_${status}`); res.setHeader('X-Request-Id', req.headers['x-request-id'] ?? 'unknown'); // Clear auth cookie on 401 if (status === HttpStatus.UNAUTHORIZED) { res.clearCookie('access_token', { path: '/' }); } res.status(status).json({ statusCode: status, message: exception.message, }); } } Express — res.setHeader('key', 'value') and res.clearCookie('name', options). Fastify — res.header('key', 'value') — setHeader() does not exist on Fastify response. To stay platform-agnostic inject HttpAdapterHost and use adapter.setHeader(res, key, value). Always set headers before calling res.status().json() — headers cannot be set after the response starts. Custom error headers like X-Error-Code or X-Request-Id help clients correlate errors with logs.

Difficulty: 6/10

Exception Filters, Response Headers, Cookies

Access the raw response object via host.switchToHttp().getResponse() and call setHeader() or clearCookie() before calling res.status().json(). For Fastify use res.header() instead of setHeader(). To stay platform-agnostic use HttpAdapterHost instead of casting to a framework-specific type.

Setting headers and cookies inside an exception filter

Platform-specific header API differences:

1
Express — res.setHeader('key', 'value') and res.clearCookie('name', options).
2
Fastify — res.header('key', 'value') — setHeader() does not exist on Fastify response.
3

How do you add custom response headers or set cookies inside an exception filter in NestJS?

Difficulty: 6/10

Exception Filters, Response Headers, Cookies

Access the raw response object via host.switchToHttp().getResponse() and call setHeader() or clearCookie() before calling res.status().json(). For Fastify use res.header() instead of setHeader(). To stay platform-agnostic use HttpAdapterHost instead of casting to a framework-specific type.

Setting headers and cookies inside an exception filter

Platform-specific header API differences:

1
Express — res.setHeader('key', 'value') and res.clearCookie('name', options).
2
Fastify — res.header('key', 'value') — setHeader() does not exist on Fastify response.
3

How do you add custom response headers or set cookies inside an exception filter in NestJS?

Access the raw response object via host.switchToHttp().getResponse() and call setHeader() or clearCookie() before calling res.status().json(). For Fastify use res.header() instead of setHeader(). To stay platform-agnostic use HttpAdapterHost instead of casting to a framework-specific type.

How do you add custom response headers or set cookies inside an exception filter in NestJS?

Access the raw response object via host.switchToHttp().getResponse() and call setHeader() or clearCookie() before calling res.status().json(). For Fastify use res.header() instead of setHeader(). To stay platform-agnostic use HttpAdapterHost instead of casting to a framework-specific type.

Scenario Questions

Follow-up Questions