What is a conditional HTTP request?
Learn how conditional requests validate cached content or help prevent an update from overwriting a resource that has changed.
Recent chatsGEEZ AT WORK
Questions, practical answers, and useful follow-ups to help you work through the details.
Showing 49–72 of 845 guides
Learn how conditional requests validate cached content or help prevent an update from overwriting a resource that has changed.
Follow a conditional request from a stored ETag through a 304 response, and see what the client can reuse—and what depends on server support.
Check the response’s Content-Type, then parse the body with error handling; a successful status alone does not confirm JSON.
A practical reference for representing spaces in URL paths and query values, including when `%20` or `+` is appropriate.
Compare possible formats for multiple values, then check the API contract so your request matches what the endpoint expects.
Classify the exact HTTP status code, distinguish receipt from completion, and record what the response actually confirms.
Learn what 500, 502, 503, and 504 communicate—and how to inspect an API response without guessing at its cause or retrying blindly.
Use common 4xx responses to choose a sensible next diagnostic question, while checking your API’s own documentation for application-specific behavior.
See which side sends each HTTP header, how to read a labeled request-and-response example, and why a header’s message matters more than its name.
Keep a control’s visible appearance and programmatic state aligned, and distinguish persistent selection from brief focus or click styling.
Review keyboard movement, date selection, dialog behavior, and a text-entry alternative so the calendar isn’t the only way to enter a date.
Specify how people move through suggestions, accept or dismiss them, and keep typing, then test each behavior with clear states.
Choose a clear name, show a value only when progress is measurable, and handle updates and completion distinctly.
Plan a keyboard-reachable dismiss control, a clear focus destination when the notice disappears, and a practical review checklist.
Test focus visibility inside nested scroll areas, check fixed overlays, and confirm keyboard users can reach both the panel and the surrounding page.
Review hidden and clipped states alongside keyboard navigation so interactive content is neither invisible while focused nor skipped when it should be available.
Plan when to validate, how to explain errors, and how to return users to a form with their entered information intact.
Review interactive controls under user-selected colors so labels, boundaries, focus, and state cues remain understandable.
Choose a semantic table or interactive grid, then define predictable keyboard movement between cells and controls before implementation.
Separate keyboard focus from selected columns with distinct visual treatments, then check both states across keyboard interactions.
Name each sortable column clearly, make the active direction understandable without its arrow or color, and review the control’s announced state.
Plan where keyboard focus goes after a view change, identify the new view clearly, and test both direct visits and in-app navigation.
Use keyboard and in-page-link checks to find when a sticky header covers a target, then adjust spacing or scrolling and retest responsive layouts.
Choose a navigation list or an application-style menu based on what it does, then test the intended tasks with both keyboard and pointer.
YOUR QUESTION. YOUR DETAILS.
Get a tailored answer or help with your next task. Starts at $1, with a quote before you pay.