Tagged articles
HTTP status codes
12 articles · Page 1 of 1
This guide teaches how to use browser developer tools (F12) to diagnose and resolve common web access anomalies—including page load failures, layout breaks, 404/500 errors, CORS issues, and data display problems—using Network, Console, Elements, and Application panels, enabling non-technical staff to identify root causes without server access.
CORSHTTP status codesapplication panel
0 likes · 21 min read

Effective API automation requires nuanced handling of HTTP status codes—beyond the simplistic 200‑success rule—by categorizing 2xx, 4xx, and 5xx responses, asserting appropriate ranges, validating business fields, and integrating unified fixtures to detect real failures, client errors, and server defects.
API testingHTTP status codesassertions
0 likes · 7 min read

The article narrates a top architect’s experience with early API error handling, the chaos caused by non‑standard HTTP status codes, the shift toward RESTful conventions, and later promotional offers for AI tools, illustrating both technical lessons and marketing pitches.
API DesignHTTP status codesRESTful
0 likes · 10 min read

This article explains how to use Python's requests library and pytest framework for interface automation testing, including HTTP status code verification and custom assertion functions.
HTTP status codespytest
0 likes · 5 min read


LouZaiOct 19, 2023 · Backend Development
This article explains what a 502 Bad Gateway error means, why it is usually generated by a reverse‑proxy like nginx, and provides step‑by‑step methods to identify common causes such as backend timeouts, process crashes, and misconfigured upstream servers.
502 Bad GatewayBackendHTTP status codes
0 likes · 15 min read

This article explains why consistent API return‑code design matters, shows how to model error codes after HTTP status segmentation, adds structured messages for both developers and end‑users, and demonstrates how unified codes enable effective monitoring and alerting.
API DesignHTTP status codeserror handling
0 likes · 6 min read

This article explains the meaning of HTTP 502 Bad Gateway errors, how reverse proxies like nginx generate them, common causes such as premature connection termination, server crashes, misconfigured upstreams, and practical steps to diagnose and fix the problem.
502HTTP status codesNginx
0 likes · 14 min read

This article explains how to design clear, consistent API return codes and messages by referencing HTTP status codes, defining code‑message pairs, supporting personalized messages for different clients, and using unified handling for monitoring and alerting, ultimately improving communication and maintenance costs.
API DesignHTTP status codeserror codes
0 likes · 6 min read

This article explains why consistent API return‑code design matters, illustrates how HTTP status code segmentation can inspire better error codes, and shows how to pair codes with customizable messages for both developers and end‑users to improve communication and maintenance efficiency.
API DesignHTTP status codeserror handling
0 likes · 4 min read

The article explains why a well‑designed API return‑code system—modeled after HTTP status codes, with clear numeric ranges, descriptive messages, and personalized user messages—reduces communication overhead, simplifies maintenance, and enables effective monitoring and alerting for backend services.
API DesignHTTP status codesbackend development
0 likes · 6 min read

This article outlines essential RESTful API design principles, covering URL structuring, proper use of HTTP verbs, precise status codes, JSON payload conventions, error handling, and HATEOAS linking, providing practical code examples for backend developers to create clear and maintainable web services.
APIHTTP status codesREST
0 likes · 8 min read

This guide explains why precise bug localization is crucial for testers, outlines systematic approaches with real-world examples, and offers practical tips—including preserving the crime scene, asking the right questions, and interpreting HTTP status codes—to efficiently identify and resolve issues across web applications.
Bug LocalizationHTTP status codesQA
0 likes · 14 min read
