[apache documentation]

Apache HTTP Server Version 1.3

Module mod_sequester

This module is contained in the mod_sequester.c file, and is not compiled into the server by default. It provides involuntary (non-credential-oriented) access control based on the time of the request.

Date Formats

This module uses the internal Apache routine parseHTTPdate to interpret the date/time strings. This means that all such strings must match one of the following formats: 

    Mon, 05 Jun 2000 08:49:37 GMT
    Monday, 05-Jun-00 08:49:37 GMT
    Mon Jun  5 08:49:39 2000

This module always interprets all dates as GMT; if a timezone is specified, it will be ignored.

Inheritance and Multiple Conditions

Inheritance of mod_sequester's configuration from one path level to the next is direct and simple: there is no merging. Each Allow* or Deny* directive within a scope completely replaces any existing condition. Since the processing of these directives is controlled by the setting of the TimeLock directive, it is possible to disable the checks for one or more path levels before reactivating them again. For example, 

    <Directory "/usr/local/PressReleases">
        TimeLock On
        AllowAfter "Mon, 05 Jun 2000 12:00:00 GMT"
    </Directory>
    <Directory "/usr/local/PressReleases/new">
        TimeLock Off
    </Directory>
    <Directory "/usr/local/PressReleases/new/FroBozz">
        TimeLock On
    </Directory>

In this example, documents in the /usr/local/PressReleases and /usr/local/PressReleases/new/FroBozz directories would be subject to the same access restrictions, but documents in the intervening path level would not be affected by them.

Directives

AllowAfter directive

Syntax: AllowAfter "GMT-time"
Default: None
Context: server config, virtual host, directory, .htaccess
Override: AuthConfig
Status: Third-party
Module: mod_sequester

The AllowAfter directive defines an access date boundary for the documents within its scope. Requests made before the specified date & time will be rejected; those made after it will be successful and allowed access to the document.

Example: 

    AllowAfter "Tue, 13 Jun 2000 08:00:00"

See the section on the date format for details of the date specification syntax.

AllowBetween directive

Syntax: AllowBetween "GMT-time" [and] "GMT-time"
Default: None
Context: server config, virtual host, directory, .htaccess
Override: AuthConfig
Status: Third-party
Module: mod_sequester

The AllowBetween directive defines a window during which access is permitted to documents within its scope. Requests made at times outside this window will result in a '403 Forbidden' status. The start and end date-times may be specified in either order, and the word 'and' may appear between them for clarity.

Example: 

    AllowBetween "Tue, 13 Jun 2000 08:00:00" and "Wed, 14 Jun 2000 17:00:00"

See the section on the date format for details of the date specification syntax.

AllowUntil directive

Syntax: AllowAfter "GMT-time"
Default: None
Context: server config, virtual host, directory, .htaccess
Override: AuthConfig
Status: Third-party
Module: mod_sequester

The AllowUntil directive permits documents within its scope to be accessed until the specified date and time arrive, after which all requests will be denied with a '403 Forbidden' status.

Example: 

    AllowUntil "Wed, 14 Jun 2000 17:00:00"

See the section on the date format for details of the date specification syntax.

DenyAfter directive

Syntax: DenyAfter "GMT-time"
Default: None
Context: server config, virtual host, directory, .htaccess
Override: AuthConfig
Status: Third-party
Module: mod_sequester

The DenyAfter directive defines an access date boundary for the documents within its scope. Requests made before the specified date & time will be rejected; those made after it will be successful and allowed access to the document.

Example: 

    DenyAfter "Tue, 13 Jun 2000 08:00:00"

See the section on the date format for details of the date specification syntax.

DenyBetween directive

Syntax: DenyBetween "GMT-time" [and] "GMT-time"
Default: None
Context: server config, virtual host, directory, .htaccess
Override: AuthConfig
Status: Third-party
Module: mod_sequester

The DenyBetween directive defines a window during which access is permitted to documents within its scope. Requests made at times outside this window will result in a '403 Forbidden' status. The start and end date-times may be specified in either order, and the word 'and' may appear between them for clarity.

Example: 

    DenyBetween "Tue, 13 Jun 2000 08:00:00" and "Wed, 14 Jun 2000 17:00:00"

See the section on the date format for details of the date specification syntax.

DenyUntil directive

Syntax: DenyUntil "GMT-time"
Default: None
Context: server config, virtual host, directory, .htaccess
Override: AuthConfig
Status: Third-party
Module: mod_sequester

The DenyUntil directive permits documents within its scope to be accessed until the specified date and time arrive, after which all requests will be denied with a '403 Forbidden' status.

Example: 

    DenyUntil "Wed, 14 Jun 2000 17:00:00"

See the section on the date format for details of the date specification syntax.

TimeLock directive

Syntax: TimeLock "On|Off"
Default: TimeLock Off
Context: server config, virtual host, directory, .htaccess
Override: AuthConfig
Status: Third-party
Module: mod_sequester

The TimeLock directive controls whether or not resources within the directive's scope are subject to access restrictions based on the request time. If set to Off, this module will not perform any access checking.

Example: 

    TimeLock On

TimeLockReport directive

Syntax: TimeLockReport "On|Off"
Default: TimeLockReport Off
Context: server config, virtual host, directory, .htaccess
Override: AuthConfig
Status: Third-party
Module: mod_sequester

When access to a document is denied, the client receives a '403 Forbidden' status page. Ordinarily this page simply says that access to the resource has been forbidden. The TimeLockReport directive controls whether or not the default '403 Forbidden' status page is replaced by one that's a little more informative. If set to On, the error page will indicate when the document was sequestered, when it will be available [again], or when the blackout period is if it was originally available and will be again.

The possible detail messages are:

  1. The resource will become available at date.
  2. The resource became unavailable at date.
  3. The resource was only available between date and date.
  4. The resource will only be available between date and date.
  5. The resource is unavailable between date and date.

Note that messages 3 and 4 are essentially identical except for the use of future or past tense.

Example: 

    TimeLockReport On

Apache HTTP Server Version 1.3

Index Home