Skip to content

Main content

HTTP Date Weekday Token Match

Compare an explicit HTTP-date weekday token with a supplied Gregorian calendar date without parsing a complete HTTP date.

Loading tool…

Description

Compare a weekday token with a supplied calendar date's UTC weekday.

Text parsers operate on an explicit source grammar and boundary policy. Recognizing delimiters or removing one prefix is distinct from validating the surrounding document or protocol. Preserve whether an output represents raw source spelling or decoded text, especially where quoted empty values, ASCII escapes, case and whitespace affect interpretation.

Compare a weekday token with a supplied calendar date's UTC weekday.

When to use this tool

Use HTTP Date Weekday Token Match when you already have calendarDate, weekdayToken and need to compare a weekday token with a supplied calendar date's UTC weekday.

How to use the tool and how it works

  1. Enter calendarDate, weekdayToken. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read matches, expectedWeekday. Inspect matches before interpreting the associated values.

Require a real YYYY-MM-DD date and token Sun through Sat; calculate the expected UTC weekday and return exact equality.1

HTTP-date includes a case-sensitive weekday name and a calendar date. This tool compares their weekday correspondence without parsing the full timestamp format.2

Input fieldMeaning and unitsAccepted input
calendarDateCalendar DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
weekdayTokenWeekday TokenRequired. Text; one of "Sun", "Mon", "Tue", "Wed", "Thu", "Fri", "Sat"; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
matchesMatchesRequired. Boolean.
expectedWeekdayExpected WeekdayRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "calendarDate": "2026-11-01",
    "weekdayToken": "Sun"
  },
  "output": {
    "matches": true,
    "expectedWeekday": "Sun"
  }
}

Limitations and assumptions

  • This checks one date/token pair, not a full HTTP-date, its allowed year form or timestamp/timezone validity.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Use a parser for the complete intended grammar and dialect when document validity matters. Keep source spelling, decoded values, quote/escape context and whitespace rules explicit; these helpers intentionally operate on one delimiter, prefix, field or protocol component.

References

  1. Calculation and input contract: parse/http-date-weekday-token-match — tool.io

  2. RFC 9110: HTTP-date — IETF

Similar or alternative tools