HTTP Status Codes Explained: What Every Number Tells Client and Server

·5 views

HTTP status codes are standardized three-digit responses that servers send back to clients after every web request, as defined by RFC 9110. They are grouped into five families: 1xx for informational, 2xx for success, 3xx for redirection, 4xx for client-side errors, and 5xx for server-side failures. Common examples include 200 OK for successful requests, 400 Bad Request when the client sends invalid data, and 500 Internal Server Error when the server encounters an unexpected fault. These codes serve as the core language of web communication, helping developers diagnose issues and build more reliable applications. Understanding them allows teams to quickly identify whether a problem originates on the client side, the server side, or somewhere in between.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

xAI Open-Sources Grok Build, Its Terminal-Based AI Coding Agent

xAI has publicly released the source code for Grok Build, a terminal-based AI coding agent designed to inspect codebases, edit files, run shell commands, search the web, and manage long-running tasks. Unlike many AI coding products that conceal implementation details behind hosted interfaces, the open-source release allows developers to study how the tool is structured, how it handles shell access, and how it manages permissions and context. The repository is organized into modular packages covering the UI, shell runtime, tools, workspace management, and sandboxing, making it more of an infrastructure project than a simple model demo. It also supports headless scripting and editor integration via the Agent Client Protocol, positioning it as a flexible foundation for building internal copilots or agent workflows. The release has drawn attention in developer communities as evidence that agent quality is increasingly an engineering challenge, not just a model capability question.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Launches Free DST-Aware Timezone Conversion API With 400+ IANA Zones

A developer has released Timezone Convert API, a free tool for converting times across more than 400 IANA timezone zones with daylight saving time awareness. The API requires no authentication key and is CORS-enabled, making it accessible for web applications. It supports multiple endpoints, including time conversion, current time lookup, UTC offset retrieval, and time-difference calculation between two zones. The service is live at timezone-convert.techtenstein.com and includes an OpenAPI 3.1 specification for developer reference. The project is released under the MIT open-source licence.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why Software Costs Spiral: Process Goals Are Quietly Overriding Product Goals

Software development costs often remain misunderstood because every system is built only once, leaving no alternative version to compare against or benchmark for quality. When systems become slow and expensive to change, the blame typically falls on complexity or shifting requirements rather than the original architectural decisions. A key driver of this problem is teams prioritising process compliance — such as closing sprint tickets on time — over building the right product. Mid-sprint discoveries that a task is wrongly scoped are frequently suppressed to meet sprint deadlines, turning a structural flaw into a recurring, invisible cost. This pattern has persisted for decades partly because it is never clearly identified as a mistake in how teams measure and reward their own work.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

IPv4 vs IPv6 Explained: How Developers Can Reliably Detect User IP Addresses

IP addresses come in two formats: IPv4, a 32-bit system with roughly 4.3 billion addresses, and IPv6, a 128-bit system designed to overcome IPv4 exhaustion with a near-unlimited address space. Developers must also distinguish between public IPs, routable on the internet, and private IPs reserved for local networks such as the 192.168.x.x range. When building backend applications, the IP a server receives is not always the true client IP, particularly when requests pass through proxies, load balancers, or CDNs like Cloudflare. In Node.js and Python, developers can read the X-Forwarded-For header to retrieve the original client IP, though the first value in the list should be treated as untrusted unless the proxy chain is controlled. Security-critical functions such as rate limiting or geofencing should never rely solely on client-reported IP headers, as these can be spoofed without proper edge-level validation.

0 comments Read more at DEV Community