All 15 HTTP & Web Servers questions
More in HTTP & Web Servers
How would you create a basic HTTP server in Node.js using only the built-in node:http module, without any framework? What is the difference between HTTP/1.1 and HTTP/2, and how does Node.js support HTTP/2 via the node:http2 module? What is HTTP keep-alive, and how does it improve performance for a Node.js server handling many requests from the same client? What is the difference between HTTP methods GET, POST, PUT, PATCH, and DELETE, and what does 'idempotent' mean in this context? What is content negotiation in HTTP, and how would a Node.js API implement it to return either JSON or XML based on a client's Accept header? What is the purpose of the HTTP OPTIONS method, and how does it relate to CORS preflight requests? What is the difference between a 301 and a 302 HTTP redirect, and when should a Node.js application use each? What is the purpose of the Content-Length and Transfer-Encoding: chunked headers, and why can't a response use both simultaneously? How would you implement Server-Sent Events (SSE) in Node.js to push real-time updates to a browser client over a single long-lived HTTP connection? How would you implement HTTP/2 server push in Node.js, and why has server push become less commonly recommended over time?
Advertisement
Node.js › HTTP & Web Servers

What is the difference between an HTTP request header and a query parameter, and when should each be used to pass information to a Node.js server?

Beginner

Answer

Headers carry metadata about the request itself (authentication tokens, content type, accepted formats) that's generally not part of the actual resource being requested, while query parameters are part of the URL and typically represent filtering, sorting, or pagination options for the specific resource being requested -- a general convention is that headers carry cross-cutting concerns applicable across many different endpoints, while query parameters carry endpoint-specific data relevant to that particular request.
// Header: cross-cutting concern (auth), same pattern across many endpoints
fetch('/api/orders', { headers: { Authorization: 'Bearer token123' } });

// Query parameters: specific to this endpoint's filtering/pagination needs
fetch('/api/orders?status=shipped&page=2&limit=20');
Real-world example An API consistently uses an Authorization header for authentication across every single endpoint (since it's a cross-cutting concern), while using endpoint-specific query parameters like ?status=shipped for filtering results, following a clear, predictable convention rather than mixing the two purposes inconsistently.

Common follow-ups: Why is it generally considered bad practice to put sensitive data like an API key in a query parameter rather than a header?;How would you decide whether a piece of data belongs in a route parameter (like /orders/:id) versus a query parameter?

Security;RESTful API Design with Express
All 15 HTTP & Web Servers questions