1 views collected around this technical thread.
This article explains common HTTP status codes, demonstrates step‑by‑step API testing using Postman—including basic requests, exception handling, token management, test assertions, and collection runs—shows how to import Postman collections into Eolinker, compares the two tools, and adds practical tips and code examples.
The article traces how an early AJAX API that used only HTTP 200 and a simple JSON wrapper devolved into a tangled mix of proper RESTful codes, custom three‑digit‑plus statuses, pseudo‑resources, PATCH work‑arounds, and finally a pragmatic scheme that keeps 200 for success, adds extended numeric categories, and adopts verb‑adjective‑resource method names for clarity.
This article explains the fundamental components of an HTTP request—including URL, methods, headers, and body—details the request‑response workflow with TCP connections, outlines common request methods and their characteristics, and categorizes response status codes for effective web development and testing.
This article explains how to design a unified JSON response format for backend services, define clear status‑code conventions, encapsulate results in a Result class, and use a custom @ResponseResult annotation together with a ResponseBodyAdvice interceptor to automatically wrap controller outputs, improving readability and error handling.
This guide outlines comprehensive backend API design recommendations, covering appropriate HTTP status codes, JSON request bodies, unique resource identifiers, timestamp formats, consistent URL structures, nested relationships, error message schemas, caching, pagination, versioning, security, and clear documentation with executable examples.
This article presents a comprehensive visual reference of all standard HTTP status codes, from informational 1xx responses to server error 5xx codes, explaining each code's meaning and typical use cases for developers working with web APIs and browsers.
This article explores the origin, technical meaning, and cultural myths of the HTTP 404 “Page Not Found” error, tracing its development from early web protocols to urban legends and even unrelated aviation incidents, while clarifying common misconceptions about its naming.
This article provides a comprehensive overview of the HTTP protocol, covering its definition, stateless nature, connection handling, key characteristics, request/response workflow, header fields, status codes, caching mechanisms, and practical applications such as resumable downloads, multithreaded downloading, proxy servers and virtual hosting.
This article outlines essential RESTful API design guidelines, covering clear URL conventions, precise HTTP status code usage, proper JSON responses, error handling without misleading 200 codes, and the inclusion of hypermedia links to improve client navigation.
This article outlines essential RESTful API design principles, covering clear URL structures, proper use of HTTP verbs, precise status codes, appropriate response formats, and the inclusion of hypermedia links to create intuitive, maintainable, and standards‑compliant web services.
This article explains essential RESTful API design details—including URL conventions, HTTP verb usage, status‑code precision, proper JSON responses, and HATEOAS linking—to help developers create clear, consistent, and user‑friendly web APIs.
This comprehensive guide walks you through the fundamentals of HTTP, covering its definition, hypertext, transfer, protocol layers, related components like browsers and servers, request‑response flow, methods, headers, status codes, content negotiation, and security extensions such as HTTPS and WAF.