HTTP Status Codes Lookup Tool

\n", "cloudImplications": "Useful in content management systems deployed in the cloud offering multiple formats.", "commonHeaders": { "Location": "Optional, preferred choice among alternatives" }, "clientReaction": "Clients may automatically follow the Location header or present choices to the user." }, "301": { "title": "Moved Permanently", "category": "3xx", "description": "The URL of the requested resource has been changed permanently. The new URL is given in the response.", "specification": "RFC 7231", "usage": "Used for permanent URL redirections. Search engines update their links to the resource.", "examples": [ "Website restructuring", "Domain name changes", "Permanent URL migrations" ], "codeExample": "HTTP/1.1 301 Moved Permanently\nLocation: https://example.com/new-page\nContent-Type: text/html", "cloudImplications": "Critical for SEO in cloud-hosted websites; search engines will update their indexes.", "commonHeaders": { "Location": "The new URL of the resource" }, "clientReaction": "Clients should update bookmarks and use the new URL for future requests.", "seoImpact": "Search engines transfer link equity to the new URL. Very important for preserving SEO value." }, "302": { "title": "Found", "category": "3xx", "description": "The URI of requested resource has been changed temporarily. New changes in the URI might be made in the future.", "specification": "RFC 7231", "usage": "Used for temporary redirections. Search engines do not update their links.", "examples": [ "Temporary promotions or campaigns", "Maintenance pages", "User redirects after login" ], "codeExample": "HTTP/1.1 302 Found\nLocation: https://example.com/temporary-page", "cloudImplications": "Commonly used during cloud deployments and maintenance windows.", "commonHeaders": { "Location": "The temporary URL of the resource" }, "clientReaction": "Clients should use the original URL for future requests.", "seoImpact": "Search engines maintain the original URL in their index but may crawl the temporary URL." }, "303": { "title": "See Other", "category": "3xx", "description": "The response to the request can be found under a different URI using a GET method.", "specification": "RFC 7231", "usage": "Used to redirect after a PUT or POST to show the result resource.", "examples": [ "Redirecting after form submission", "POST-Redirect-GET pattern", "Directing users to a receipt page after payment" ], "codeExample": "HTTP/1.1 303 See Other\nLocation: https://example.com/order/12345", "cloudImplications": "Important for cloud-based e-commerce and form handling to prevent duplicate submissions.", "commonHeaders": { "Location": "The URL where the response can be found" }, "clientReaction": "Clients should follow the redirect with a GET request regardless of the original method." }, "304": { "title": "Not Modified", "category": "3xx", "description": "The resource has not been modified since the last request.", "specification": "RFC 7232", "usage": "Used with conditional requests to reduce bandwidth and processing.", "examples": [ "Browser cache validation", "API responses with ETag validation", "Efficient content delivery" ], "codeExample": "HTTP/1.1 304 Not Modified\nETag: \"33a64df551425fcc55e4d42a148795d9f25f89d4\"\nCache-Control: max-age=3600", "cloudImplications": "Critical for reducing bandwidth costs and improving performance in cloud applications.", "commonHeaders": { "ETag": "Entity tag for the unmodified resource", "Cache-Control": "Caching directives", "Last-Modified": "When the resource was last changed" }, "clientReaction": "Clients should use their cached copy of the resource.", "performance": "Significantly improves performance by avoiding unnecessary data transfers." }, "305": { "title": "Use Proxy", "category": "3xx", "description": "The requested resource must be accessed through the proxy given by the Location field.", "specification": "RFC 7231", "usage": "Deprecated due to security concerns.", "examples": [ "Corporate proxies requiring specific access methods", "Historical content gateways" ], "codeExample": "HTTP/1.1 305 Use Proxy\nLocation: http://proxy.example.com:8080", "cloudImplications": "Generally not used in modern cloud architectures due to security concerns.", "commonHeaders": { "Location": "The proxy URL that should be used" }, "clientReaction": "Clients should resubmit the request through the specified proxy.", "securityConcerns": "Could be used for phishing, which led to its deprecation." }, "307": { "title": "Temporary Redirect", "category": "3xx", "description": "The request should be repeated with another URI, but future requests should still use the original URI.", "specification": "RFC 7231", "usage": "Similar to 302, but guarantees the request method won't change.", "examples": [ "Load balancing", "Temporary service migration", "A/B testing" ], "codeExample": "HTTP/1.1 307 Temporary Redirect\nLocation: https://mirror.example.com/resource", "cloudImplications": "Important for maintaining RESTful principles in cloud services during temporary changes.", "commonHeaders": { "Location": "The temporary URL of the resource" }, "clientReaction": "Clients must use the same HTTP method when following the redirect.", "difference302": "Unlike 302, a POST request will remain a POST after redirection." }, "308": { "title": "Permanent Redirect", "category": "3xx", "description": "The request and all future requests should be repeated using another URI.", "specification": "RFC 7538", "usage": "Similar to 301, but guarantees the request method won't change.", "examples": [ "API endpoint permanent migration", "Permanent restructuring requiring method preservation" ], "codeExample": "HTTP/1.1 308 Permanent Redirect\nLocation: https://api.newdomain.com/v2/resource", "cloudImplications": "Ensures method preservation during permanent migrations in cloud services.", "commonHeaders": { "Location": "The new URL of the resource" }, "clientReaction": "Clients must use the same HTTP method when following the redirect and for all future requests.", "difference301": "Unlike 301, a POST request will remain a POST after redirection, preventing data loss." }, // 4xx Client Errors "400": { "title": "Bad Request", "category": "4xx", "description": "The server could not understand the request due to invalid syntax.", "specification": "RFC 7231", "usage": "Used when the request is malformed, has missing parameters, or contains invalid data.", "examples": [ "Invalid JSON formatting in request body", "Missing required parameters", "Syntax errors in the request" ], "codeExample": "HTTP/1.1 400 Bad Request\nContent-Type: application/json\n\n{\"error\": \"Invalid request\", \"details\": \"Missing required field: email\"}", "cloudImplications": "Common in cloud APIs for input validation; should include clear error messages for debugging.", "commonHeaders": { "Content-Type": "Usually application/json for API errors" }, "clientReaction": "The client should fix the request before resubmitting.", "bestPractices": "Include specific error details and validation information in the response body." }, "401": { "title": "Unauthorized", "category": "4xx", "description": "Authentication is required and has failed or has not yet been provided.", "specification": "RFC 7235", "usage": "Used when authentication is needed but was not provided or was invalid.", "examples": [ "Missing authentication token", "Invalid credentials", "Expired access tokens" ], "codeExample": "HTTP/1.1 401 Unauthorized\nWWW-Authenticate: Bearer realm=\"example\"\nContent-Type: application/json\n\n{\"error\": \"Authentication required\"}", "cloudImplications": "Critical for securing cloud services and APIs.", "commonHeaders": { "WWW-Authenticate": "Authentication scheme required", "Content-Type": "Usually application/json for API errors" }, "clientReaction": "The client should provide valid authentication credentials.", "securityBestPractices": "Don't expose sensitive details in error messages; provide only enough information for proper authentication." }, "402": { "title": "Payment Required", "category": "4xx", "description": "Reserved for future use. Originally intended for digital payment systems.", "specification": "RFC 7231", "usage": "Currently rarely used, though sometimes indicates a need to pay for a service.", "examples": [ "Subscription services requiring payment", "API usage beyond free tier limits", "Paywall content" ], "codeExample": "HTTP/1.1 402 Payment Required\nContent-Type: application/json\n\n{\"error\": \"Payment required\", \"plans\": [\"basic\", \"premium\"], \"upgradeUrl\": \"https://example.com/upgrade\"}", "cloudImplications": "Occasionally used in SaaS and cloud services to indicate subscription requirements.", "clientReaction": "The client needs to complete a payment or subscription process to access the resource.", "implementation": "Not standardized; implementations vary widely between services." }, "403": { "title": "Forbidden", "category": "4xx", "description": "The client does not have access rights to the content; that is, it is unauthorized.", "specification": "RFC 7231", "usage": "Used when the client is authenticated but not allowed to access the requested resource.", "examples": [ "Accessing admin resources as regular user", "Trying to modify read-only resources", "Geographic or role-based access restrictions" ], "codeExample": "HTTP/1.1 403 Forbidden\nContent-Type: application/json\n\n{\"error\": \"Access denied\", \"reason\": \"Insufficient permissions\"}", "cloudImplications": "Essential for enforcing permissions and access controls in cloud applications.", "commonHeaders": { "Content-Type": "Usually application/json for API errors" }, "clientReaction": "The client should not repeat the request without elevated permissions.", "security": "Unlike 401, authentication won't help - the user lacks proper authorization.", "difference401": "401 means 'you need to authenticate'; 403 means 'you're authenticated but not allowed'." }, "404": { "title": "Not Found", "category": "4xx", "description": "The server can not find the requested resource.", "specification": "RFC 7231", "usage": "The most common error, indicating the requested URL doesn't exist on the server.", "examples": [ "Broken links", "Deleted resources", "Mistyped URLs" ], "codeExample": "HTTP/1.1 404 Not Found\nContent-Type: text/html\n\n\n\n

Not Found

\n

The requested resource was not found on this server.

\n \n", "cloudImplications": "Important for proper error handling in cloud applications; customize for better user experience.", "commonHeaders": { "Content-Type": "Type of error content (HTML, JSON, etc.)" }, "clientReaction": "The client should check the URL and navigation path.", "bestPractices": "Customize 404 pages to help users find what they're looking for instead of leaving the site.", "seoImpact": "Too many 404s can negatively impact SEO; implement proper redirects for moved content." }, "405": { "title": "Method Not Allowed", "category": "4xx", "description": "The request method is known by the server but is not supported by the target resource.", "specification": "RFC 7231", "usage": "Used when an HTTP method (GET, POST, etc.) is not allowed for the requested resource.", "examples": [ "Trying to POST to a read-only resource", "Using DELETE on a protected resource", "Using PUT when only POST is allowed" ], "codeExample": "HTTP/1.1 405 Method Not Allowed\nAllow: GET, HEAD\nContent-Type: application/json\n\n{\"error\": \"Method not allowed\", \"allowed\": [\"GET\", \"HEAD\"]}", "cloudImplications": "Important for RESTful API design in cloud services.", "commonHeaders": { "Allow": "List of allowed HTTP methods", "Content-Type": "Usually application/json for API errors" }, "clientReaction": "The client should use one of the allowed methods instead.", "apiDesign": "Always include the Allow header to inform clients which methods are permitted." }, "406": { "title": "Not Acceptable", "category": "4xx", "description": "The server cannot produce a response matching the list of acceptable values.", "specification": "RFC 7231", "usage": "Used when content negotiation fails, e.g., when the client's Accept headers can't be satisfied.", "examples": [ "Requesting JSON when only XML is available", "Asking for a language version that doesn't exist", "Media type negotiation failures" ], "codeExample": "HTTP/1.1 406 Not Acceptable\nContent-Type: application/json\n\n{\"error\": \"Not acceptable\", \"available\": [\"text/html\", \"application/xml\"], \"requested\": \"application/json\"}", "cloudImplications": "Important for APIs and content delivery services that support multiple formats.", "commonHeaders": { "Content-Type": "Format used for the error message" }, "clientReaction": "The client should modify its Accept headers to allow one of the available formats." }, "407": { "title": "Proxy Authentication Required", "category": "4xx", "description": "Similar to 401 but authentication is needed at the proxy level.", "specification": "RFC 7235", "usage": "Used when a proxy server requires authentication before forwarding the request.", "examples": [ "Corporate proxy authentication", "Network gateway authentication", "Access control at proxy level" ], "codeExample": "HTTP/1.1 407 Proxy Authentication Required\nProxy-Authenticate: Basic realm=\"Proxy\"\nContent-Type: text/html", "cloudImplications": "Relevant for enterprise cloud deployments with proxy-based security.", "commonHeaders": { "Proxy-Authenticate": "Authentication scheme required by the proxy" }, "clientReaction": "The client must authenticate with the proxy before the request can proceed." }, "408": { "title": "Request Timeout", "category": "4xx", "description": "The server timed out waiting for the request.", "specification": "RFC 7231", "usage": "Used when a client takes too long to complete sending its request.", "examples": [ "Slow network connections", "Client starting a request but not completing it", "Excessive processing time on the client side" ], "codeExample": "HTTP/1.1 408 Request Timeout\nConnection: close", "cloudImplications": "Important for managing resources in cloud environments; prevents hung connections.", "commonHeaders": { "Connection": "Usually 'close'" }, "clientReaction": "The client should retry the request, preferably faster or with a more reliable connection.", "serverConfig": "Timeout values are configurable in most cloud servers and load balancers." }, "409": { "title": "Conflict", "category": "4xx", "description": "The request could not be processed because of conflict in the current state of the resource.", "specification": "RFC 7231", "usage": "Used when a request conflicts with the current state of the server, e.g., version conflicts.", "examples": [ "Trying to update a resource that has been modified by another user", "Attempting to create a resource that already exists", "Version control conflicts" ], "codeExample": "HTTP/1.1 409 Conflict\nContent-Type: application/json\n\n{\"error\": \"Conflict\", \"message\": \"Resource has been modified by another request\", \"currentVersion\": \"2\", \"yourVersion\": \"1\"}", "cloudImplications": "Critical for maintaining data integrity in distributed cloud systems.", "clientReaction": "The client should resolve the conflict and resubmit, possibly by retrieving the current state first.", "dataIntegrity": "Often includes version information to help clients resolve the conflict." }, "410": { "title": "Gone", "category": "4xx", "description": "The requested resource is no longer available and will not be available again.", "specification": "RFC 7231", "usage": "Used for resources that have been permanently removed.", "examples": [ "Accessing a deleted blog post", "Expired temporary content", "Resources from discontinued services" ], "codeExample": "HTTP/1.1 410 Gone\nContent-Type: application/json\n\n{\"error\": \"Resource permanently removed\", \"details\": \"This content has been permanently deleted.\"}", "cloudImplications": "Better than 404 for explicitly removed resources; helps with SEO in cloud-hosted sites.", "clientReaction": "The client should remove references to the resource, as it will not be available again.", "seoImpact": "Search engines handle 410 differently than 404, more quickly removing the resource from indexes." }, "411": { "title": "Length Required", "category": "4xx", "description": "The server refuses to accept the request without a defined Content-Length.", "specification": "RFC 7231", "usage": "Used when the Content-Length header is missing but required for the request.", "examples": [ "File uploads without content length", "Streaming content without proper headers", "Malformed POST requests" ], "codeExample": "HTTP/1.1 411 Length Required\nContent-Type: application/json\n\n{\"error\": \"Content-Length header is required for this request\"}", "cloudImplications": "Important for security and resource management in cloud services.", "clientReaction": "The client must include a valid Content-Length header in the request." }, "412": { "title": "Precondition Failed", "category": "4xx", "description": "The server does not meet one of the preconditions specified in the request headers.", "specification": "RFC 7232", "usage": "Used with conditional requests when the condition (like If-Match) is not met.", "examples": [ "ETags not matching in conditional updates", "Modified dates in If-Unmodified-Since not being satisfied", "Optimistic concurrency control" ], "codeExample": "HTTP/1.1 412 Precondition Failed\nETag: \"33a64df551425fcc55e4d42a148795d9f25f89d4\"\nContent-Type: application/json\n\n{\"error\": \"Precondition failed\", \"message\": \"Resource has been modified\"}", "cloudImplications": "Critical for maintaining data consistency in distributed cloud systems.", "commonHeaders": { "ETag": "Current entity tag of the resource" }, "clientReaction": "The client should get the current state of the resource before attempting to modify it again." }, "413": { "title": "Payload Too Large", "category": "4xx", "description": "The request entity is larger than limits defined by server.", "specification": "RFC 7231", "usage": "Used when a client attempts to upload a file that exceeds the server's size limit.", "examples": [ "Uploading files exceeding size limits", "Submitting extremely large forms", "API requests with too much data" ], "codeExample": "HTTP/1.1 413 Payload Too Large\nContent-Type: application/json\n\n{\"error\": \"Payload too large\", \"maxSize\": \"10MB\", \"yourSize\": \"25MB\"}", "cloudImplications": "Important for protecting cloud resources from excessive data and potential DoS attacks.", "commonHeaders": { "Retry-After": "Optional, when the server might accept the payload later" }, "clientReaction": "The client should reduce the size of the request payload.", "serverConfig": "Size limits are typically configurable in cloud server environments." }, "414": { "title": "URI Too Long", "category": "4xx", "description": "The URI requested by the client is longer than the server is willing to interpret.", "specification": "RFC 7231", "usage": "Used when a URL is too long, often due to excessive query parameters.", "examples": [ "URLs with too many query parameters", "Deep nested paths beyond server limits", "Excessively lengthy encoded data in URLs" ], "codeExample": "HTTP/1.1 414 URI Too Long\nContent-Type: application/json\n\n{\"error\": \"URI too long\", \"maxLength\": 2048, \"yourLength\": 2500}", "cloudImplications": "Protective measure in cloud environments; consider using POST with body instead of long query strings.", "clientReaction": "The client should shorten the URI, possibly by using fewer parameters or switching to POST with a request body.", "bestPractices": "For complex queries, use POST requests with the parameters in the request body." }, "415": { "title": "Unsupported Media Type", "category": "4xx", "description": "The media format of the requested data is not supported by the server.", "specification": "RFC 7231", "usage": "Used when the content type of the request body isn't supported, e.g., sending JSON to an XML-only API.", "examples": [ "Sending XML to a JSON-only API", "Uploading images in unsupported formats", "Content type header mismatches" ], "codeExample": "HTTP/1.1 415 Unsupported Media Type\nContent-Type: application/json\n\n{\"error\": \"Unsupported media type\", \"supported\": [\"application/json\"], \"received\": \"application/xml\"}", "cloudImplications": "Common in cloud APIs with specific format requirements.", "clientReaction": "The client should reformat the data using one of the supported content types.", "apiDesign": "API documentation should clearly specify supported content types." }, "416": { "title": "Range Not Satisfiable", "category": "4xx", "description": "The range specified in the Range header cannot be fulfilled.", "specification": "RFC 7233", "usage": "Used when the requested range in a Range header can't be satisfied, e.g., beyond file boundaries.", "examples": [ "Requesting bytes beyond the end of a file", "Invalid range formats", "Range not supported for the specific resource" ], "codeExample": "HTTP/1.1 416 Range Not Satisfiable\nContent-Range: bytes */12345\nContent-Type: application/json", "cloudImplications": "Important for cloud storage and streaming services supporting partial content requests.", "commonHeaders": { "Content-Range": "Indicates the entire size with */size format" }, "clientReaction": "The client should adjust the range request to be within valid boundaries." }, "417": { "title": "Expectation Failed", "category": "4xx", "description": "The expectation given in the Expect request header could not be met.", "specification": "RFC 7231", "usage": "Used when the Expect header requirements can't be met by the server.", "examples": [ "Server unable to handle 100-continue expectation", "Custom expectations not supported by the server" ], "codeExample": "HTTP/1.1 417 Expectation Failed\nContent-Type: application/json\n\n{\"error\": \"Server cannot meet the expectation specified in the Expect header\"}", "cloudImplications": "May occur in complex cloud deployments with varying server capabilities across nodes." }, // More 4xx client errors "429": { "title": "Too Many Requests", "category": "4xx", "description": "The user has sent too many requests in a given amount of time.", "specification": "RFC 6585", "usage": "Used for rate limiting to prevent abuse or overloading of services.", "examples": [ "API rate limits being exceeded", "Brute force login protection", "DDoS protection measures" ], "codeExample": "HTTP/1.1 429 Too Many Requests\nRetry-After: 60\nContent-Type: application/json\n\n{\"error\": \"Rate limit exceeded\", \"retryAfter\": \"60 seconds\", \"limit\": \"100 requests per minute\"}", "cloudImplications": "Essential for protecting cloud services from abuse and ensuring fair resource allocation.", "commonHeaders": { "Retry-After": "Seconds to wait before making another request" } }, // 5xx Server Errors "500": { "title": "Internal Server Error", "category": "5xx", "description": "The server has encountered a situation it doesn't know how to handle.", "specification": "RFC 7231", "usage": "A generic error message when an unexpected condition was encountered on the server.", "examples": [ "Programming errors", "Database connection failures", "Unexpected exceptions in server-side code" ], "codeExample": "HTTP/1.1 500 Internal Server Error\nContent-Type: application/json\n\n{\"error\": \"Internal server error\", \"requestId\": \"xyz-123\"}", "cloudImplications": "Critical to monitor in cloud environments; often indicates application bugs or resource issues.", "bestPractices": "Include logging identifiers to correlate user-facing errors with internal logs." }, "502": { "title": "Bad Gateway", "category": "5xx", "description": "The server, while acting as a gateway or proxy, received an invalid response from the upstream server.", "specification": "RFC 7231", "usage": "Used when a gateway or proxy server gets an invalid response from an upstream server.", "examples": [ "Reverse proxy unable to connect to backend", "Microservices communication failures", "Invalid responses from third-party APIs" ], "codeExample": "HTTP/1.1 502 Bad Gateway\nContent-Type: application/json\n\n{\"error\": \"Bad gateway\", \"details\": \"Upstream server returned an invalid response\"}", "cloudImplications": "Common in microservices architectures and multi-tier cloud applications." }, "503": { "title": "Service Unavailable", "category": "5xx", "description": "The server is not ready to handle the request, often due to maintenance or overloading.", "specification": "RFC 7231", "usage": "Used for temporary server outages, maintenance windows, or overload situations.", "examples": [ "Server maintenance periods", "Traffic overloads", "Resource exhaustion" ], "codeExample": "HTTP/1.1 503 Service Unavailable\nRetry-After: 3600\nContent-Type: application/json\n\n{\"error\": \"Service unavailable\", \"maintenance\": \"Scheduled maintenance until 14:00 UTC\"}", "cloudImplications": "Important for graceful handling of scaling events and planned maintenance in cloud services.", "commonHeaders": { "Retry-After": "Estimate of when service will be available" } } }; // Get DOM elements const statusInput = document.getElementById('status-input'); const lookupButton = document.getElementById('lookup-button'); const clearButton = document.getElementById('clear-button'); const singleResult = document.getElementById('single-result'); const multipleResults = document.getElementById('multiple-results'); const statusMessage = document.getElementById('status-message'); const suggestionsList = document.getElementById('suggestions'); const quickOptions = document.querySelectorAll('.quick-option'); // Function to look up HTTP status code function lookupStatusCode() { const query = statusInput.value.trim(); // Hide suggestions suggestionsList.style.display = 'none'; // Clear previous results singleResult.innerHTML = ''; multipleResults.innerHTML = ''; // Hide status message statusMessage.style.display = 'none'; if (!query) { showStatus('Please enter a status code or keyword to search.', 'invalid'); return; } // Check if input is a valid status code if (/^\d{3}$/.test(query) && httpStatusCodes[query]) { // Display single status code displaySingleStatusCode(query); } else { // Search by keyword const results = searchStatusCodesByKeyword(query); if (results.length > 0) { displayMultipleStatusCodes(results); } else { showStatus('No HTTP status codes found matching your query. Try a different search term.', 'invalid'); } } } // Function to display a single status code with enhanced details function displaySingleStatusCode(code) { const statusCode = httpStatusCodes[code]; const categoryClass = `status-${statusCode.category.substring(0,1)}xx`; let examplesHTML = ''; if (statusCode.examples && statusCode.examples.length > 0) { examplesHTML = ` `; } let codeExampleHTML = ''; if (statusCode.codeExample) { codeExampleHTML = ` `; } singleResult.innerHTML = ` `; } // Function to display multiple status codes function displayMultipleStatusCodes(results) { if (results.length === 1) { // If only one result, display as single displaySingleStatusCode(results[0]); return; } // Group results by category const groupedResults = groupByCategory(results); // Display status message showStatus(`Found ${results.length} HTTP status codes matching your query.`, 'valid'); // Display grouped results let resultsHTML = ''; for (const category in groupedResults) { if (groupedResults[category].length > 0) { resultsHTML += `

${getCategoryName(category)}

`; for (const code of groupedResults[category]) { const statusCode = httpStatusCodes[code]; const categoryClass = `status-${statusCode.category.substring(0,1)}xx`; resultsHTML += ` `; } } } multipleResults.innerHTML = resultsHTML; } // Function to provide suggestions as user types function provideSuggestions(query) { // Clear existing suggestions suggestionsList.innerHTML = ''; if (!query || query.length < 2) { suggestionsList.style.display = 'none'; return; } const lowerQuery = query.toLowerCase(); let matches = []; // First look for exact code matches if (/^\d+$/.test(query)) { for (const code in httpStatusCodes) { if (code.startsWith(query)) { matches.push({ code: code, title: httpStatusCodes[code].title }); } } } // Then look for title/keyword matches for (const code in httpStatusCodes) { const statusCode = httpStatusCodes[code]; if (statusCode.title.toLowerCase().includes(lowerQuery)) { // Avoid duplicates if (!matches.some(match => match.code === code)) { matches.push({ code: code, title: statusCode.title }); } } } // Limit to top 6 matches matches = matches.slice(0, 6); if (matches.length > 0) { matches.forEach(match => { const item = document.createElement('div'); item.className = 'suggestion-item'; item.innerHTML = `${match.code} ${match.title}`; item.addEventListener('click', () => { statusInput.value = match.code; suggestionsList.style.display = 'none'; lookupStatusCode(); }); suggestionsList.appendChild(item); }); suggestionsList.style.display = 'block'; } else { suggestionsList.style.display = 'none'; } } // Function to search status codes by keyword function searchStatusCodesByKeyword(keyword) { const lowerKeyword = keyword.toLowerCase(); const results = []; // Search through all status codes for (const code in httpStatusCodes) { const statusCode = httpStatusCodes[code]; // Check if keyword is in title, description, or usage if ( statusCode.title.toLowerCase().includes(lowerKeyword) || statusCode.description.toLowerCase().includes(lowerKeyword) || statusCode.usage.toLowerCase().includes(lowerKeyword) ) { results.push(code); } } return results; } // Function to group results by category function groupByCategory(codes) { const grouped = { '1xx': [], '2xx': [], '3xx': [], '4xx': [], '5xx': [] }; for (const code of codes) { const statusCode = httpStatusCodes[code]; grouped[statusCode.category].push(code); } return grouped; } // Function to get category name function getCategoryName(category) { switch (category) { case '1xx': return 'Informational (1xx)'; case '2xx': return 'Success (2xx)'; case '3xx': return 'Redirection (3xx)'; case '4xx': return 'Client Error (4xx)'; case '5xx': return 'Server Error (5xx)'; default: return category; } } // Function to get category color function getCategoryColor(category) { switch (category) { case '1xx': return '#6c757d'; case '2xx': return '#28a745'; case '3xx': return '#17a2b8'; case '4xx': return '#ffc107'; case '5xx': return '#dc3545'; default: return '#6c757d'; } } // Function to show status message function showStatus(message, status) { const statusDiv = document.getElementById('status-message'); statusDiv.textContent = message; statusDiv.className = `tool-status tool-${status}`; statusDiv.style.display = 'block'; } // Function to clear all inputs and results function clearAll() { statusInput.value = ''; singleResult.innerHTML = ''; multipleResults.innerHTML = ''; statusMessage.style.display = 'none'; suggestionsList.style.display = 'none'; } // When the page loads, attach event handlers document.addEventListener('DOMContentLoaded', function() { // Lookup button event listener lookupButton.addEventListener('click', lookupStatusCode); // Clear button event listener clearButton.addEventListener('click', clearAll); // Quick option buttons quickOptions.forEach(option => { option.addEventListener('click', function() { const code = this.getAttribute('data-code'); statusInput.value = code; lookupStatusCode(); }); }); // Input field events for suggestions statusInput.addEventListener('input', function() { provideSuggestions(this.value.trim()); }); // Hide suggestions when clicking outside document.addEventListener('click', function(e) { if (e.target !== statusInput && e.target !== suggestionsList) { suggestionsList.style.display = 'none'; } }); // Allow pressing Enter in the input field statusInput.addEventListener('keydown', function(e) { if (e.key === 'Enter') { lookupStatusCode(); e.preventDefault(); } }); // Focus on input field by default statusInput.focus(); // Populate with a sample if empty and tool is clicked document.querySelector('.tool-content').addEventListener('click', function(e) { if (statusInput.value === '' && e.target === this) { statusInput.focus(); } }); });