day=

Tests if the day of the month is in the specified range or an exact match. The appliance’s configured date and time zone are used to determine the current day of the month. To specify the UTC time zone, use the form day.utc=. The numeric pattern used to test the day condition cannot contain whitespace.

Syntax

day[.utc]={[
first_day
]..[
last_day
]|
exact_day
}
where:
  • first_day
    : Integer from 1 to 31, indicating the first day of the month that will test true. If left blank, day 1 is assumed.
  • last_day
    : Integer from 1 to 31, indicating the last day of the month that will test true. If left blank, day 31 is assumed.
  • exact_day
    : Integer from 1 to 31, indicating the day of the month that will test true.
To test against an inverted range, such as days early and late in the month, a shorthand expression is available. Whereas
day=(..5|25..)
specifies the first 5 days of the month and last few days of the month, the policy language also recognizes
day=25..5
as the same.

Layer and Transaction Notes

  • Layers:
    <Admin>
    ,
    <Cache>
    ,
    <Diagnostic>
    ,
    <DNS-Proxy>
    ,
    <Exception>
    ,
    <Forward>
    ,
    <Proxy>
    ,
    <SSL>
    ,
    <SSL-Intercept>
  • Transactions: all
Using time-related conditions to control caching behavior in a
<Cache>
layer may cause thrashing of the cached objects.

Example 1

Test for New Year's Day.
<Proxy> day=1 month=1

Example 2

Allow access to a special event site only during the days of the event. Restrict access during non-event times.
<Proxy> url=http://www.xyz.com/special_event ; The next line matches, but does nothing if allow is the default ; year=2023 month=7 day=23..25 ; During the event ; deny Any other time ; This form of the rule assumes access is generally denied, and grants access during ; the special event. <Proxy> url=http://www.xyz.com/special_event allow year=2023 month=7 day=23..25 ; During the event

See Also