Dm

Не подскажет ли уважаемый All ссылку на сабж?
Просьба: к RFC2068 не отсылать.

@stilia

Вот тут все (или почти все) переменные, которые передаются в через хэшик %ENV
http://stilia.agava.ru/help/cgi/env.html

0

Dm

Спасибо, stilia.

@-Dark-

2Dm

А почему бы и нет? Могу дать русский вариант RFC! Все просто и понятно.

0

Dm

Спасибо, я уже порылся в rfc (cм. ниже).
Только rfc2068 ответ не ограничивается, к сожалению.

request-header = Accept ; Section 14.1
| Accept-Charset ; Section 14.2
| Accept-Encoding ; Section 14.3
| Accept-Language ; Section 14.4
| Authorization ; Section 14.8
| From ; Section 14.22
| Host ; Section 14.23
| If-Modified-Since ; Section 14.24
| If-Match ; Section 14.25
| If-None-Match ; Section 14.26
| If-Range ; Section 14.27
| If-Unmodified-Since ; Section 14.28
| Max-Forwards ; Section 14.31
| Proxy-Authorization ; Section 14.34
| Range ; Section 14.36
| Referer ; Section 14.37
| User-Agent ; Section 14.42

general-header = Cache-Control ; Section 14.9
| Connection ; Section 14.10
| Date ; Section 14.19
| Pragma ; Section 14.32
| Transfer-Encoding ; Section 14.40
| Upgrade ; Section 14.41
| Via ; Section 14.44


rfc2068
ACCEPT
The Accept request-header field can be used to specify certain media
types which are acceptable for the response. Accept headers can be used
to indicate that the request is specifically limited to a small set of
desired types, as in the case of a request for an in-line image.
text/plain; q=0.5, text/html, text/x-dvi; q=0.8, text/x-c или text/*,
text/html, text/html;level=1, */*
request-header

rfc2068
ACCEPT_CHARSET
The Accept-Charset request-header field can be used to indicate what
character sets are acceptable for the response. This field allows
clients capable of understanding more comprehensive or special- purpose
character sets to signal that capability to a server which is capable of
representing documents in those character sets. The ISO- 8859-1
character set can be assumed to be acceptable to all user agents.
iso-8859-5, unicode-1-1;q=0.8
request-header

rfc2068
ACCEPT_ENCODING
The Accept-Encoding request-header field is similar to Accept, but
restricts the content-coding values (section 14.12) which are acceptable
in the response.
compress, gzip
request-header

rfc2068
ACCEPT_LANGUAGE
The Accept-Language request-header field is similar to Accept, but
restricts the set of natural languages that are preferred as a response
to the request.
da, en-gb;q=0.8, en;q=0.7
request-header

rfc2068
ACCEPT_RANGES
The Accept-Ranges response-header field allows the server to indicate
its acceptance of range requests for a resource:
none
response-header

rfc2068
AGE
The Age response-header field conveys the sender's estimate of the
amount of time since the response (or its revalidation) was generated at
the origin server. A cached response is 'fresh' if its age does not
exceed its freshness lifetime.
response-header

rfc2068
ALLOW
The Allow entity-header field lists the set ld indicates the media type of the
entity-body sent to the recipient or, in the case of the HEAD method,
the media type that would have been sent had the request been a GET.
entity-header

rfc2068
CONTENT_TYPE
The Content-Type entity-header field indicates the media type of the
entity-body sent to the recipient or, in the case of the HEAD method,
the media type that would have been sent had the request been a GET.
entity-header

rfc2068
CONTENT-MD5
The Content-MD5 entity-header field, as defined in RFC 1864 [23], is an
MD5 digest of the entity-body for the purpose of providing an end-to-end
message integrity check (MIC) of the entity-body.
entity-header

rfc2068
DATE
The Date general-header field represents the date and time at which the
message was originated, having the same semantics as orig-date in RFC
822.
Tue, 15 Nov 1994 08:12:31 GMT
general-header

rfc2068
ETAG
The ETag entity-header field defines the entity tag for the associated
entity.
entity-header

rfc2068
EXPIRES
The Expires entity-header field gives the date/time after which the
response should be considered stale. A stale cache entry may not
normally be returned by a cache (either a proxy cache or an user agent
cache) unless it is first validated with the origin server (or with an
intermediate cache that has a fresh copy of the entity).
Thu, 01 Dec 1994 16:00:00 GMT
entity-header

rfc2068
FROM
The From request-header field, if given, SHOULD contain an Internet
e-mail address for the human user who controls the requesting user
agent. The address SHOULD be machine-usable, as defined by mailbox in
RFC 822 (as updated by RFC 1123 ):
webmaster@w3.org
request-header

rfc2068
HOST
The Host request-header field specifies the Internet host and port
number of the resource being requested, as obtained from the original
URL given by the user or referring resource
www.w3.org
request-header

rfc2068
IF_MATCH
The If-Match request-header field is used with a method to make it
conditional. A client that has one or more entities previously obtained
from the resource can verify that one of those entities is current by
including a list of their associated entity tags in the If-Match header
field.
request-header

rfc2068
IF_MODIFIED_SINCE
The If-Modified-Since request-header field is used with the GET method
to make it conditional: if the requested variant has not been modified
since the time specified in this field, an entity will not be returned
from the server; instead, a 304 (not modified) response will be returned
without any message-body.
Sat, 29 Oct 1994 19:43:31 GMT
request-header

rfc2068
IF_NONE_MATCH
The If-None-Match request-header field is used with a method to make it
conditional. A client that has one or more entities previously obtained
from the resource can verify that none of those entities is current by
including a list of their associated entity tags in the If-None-Match
header field.
request-header

rfc2068
IF_RANGE
If a client has a partial copy of an entity in its cache, and wishes to have an up-to-date copy of the entire entity in its cache, it could use the Range request-header with a conditional GET (using either or both of If-Unmodified-Since and If-Match.)
request-header

rfc2068
IF_UNMODIFIED_SINCE
The If-Unmodified-Since request-header field is used with a method to
make it conditional. If the requested resource has not been modified
since the time specified in this field, the server should perform the
requested operation as if the If-Unmodified-Since header were not
present.
Sat, 29 Oct 1994 19:43:31 GMT
request-header

rfc2068
LAST_MODIFIED
The Last-Modified entity-header field indicates the date and time at
which the origin server believ R>
rfc2068
VIA
The Via general-header field MUST be used by gateways and proxies to
indicate the intermediate protocols and recipients between the user
agent and the server on requests, and between the origin server and the
client on responses.
general-header

rfc2068
WARNING
The Warning response-header field is used to carry additional
information about the status of a response which may not be reflected by
the response status code. This information is typically, though not
exclusively, used to warn about a possible lack of semantic transparency
from caching operations.
response-header

rfc2068
WWW_AUTHENTICATE
The WWW-Authenticate response-header field MUST be included in 401
(Unauthorized) response messages. The field value consists of at least
one challenge that indicates the authentication scheme(s) and parameters
applicable to the Request-URI.
response-header