|
|
|
Supreme Being
участник
Last Login: 08.08.2002 15:06
Сообщ.: 168,
Visits: 1 970
|
|
Не подскажет ли уважаемый All ссылку на сабж?
Просьба: к RFC2068 не отсылать. :)
|
|
|
|
|
новичок
участник
Last Login: 09.11.2001 15:41
Сообщ.: 6,
Visits: 67
|
|
Вот тут все (или почти все) переменные, которые передаются в через хэшик %ENV
http://stilia.agava.ru/help/cgi/env.html
|
|
|
|
|
Supreme Being
участник
Last Login: 08.08.2002 15:06
Сообщ.: 168,
Visits: 1 970
|
|
|
|
|
|
Supreme Being
участник
Last Login: 15.03.2003 7:02
Сообщ.: 88,
Visits: 980
|
|
2Dm
А почему бы и нет? Могу дать русский вариант RFC! Все просто и понятно.
|
|
|
|
|
Supreme Being
участник
Last Login: 08.08.2002 15:06
Сообщ.: 168,
Visits: 1 970
|
|
Спасибо, я уже порылся в 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 of methods supported by the
resource identified by the Request-URI. The purpose of this field is
strictly to inform the recipient of valid methods associated with the
resource. An Allow header field MUST be present in a 405 (Method Not
Allowed) response.
entity-header
rfc2068
ALTERNATES
Reserved
request-header
rfc2068
AUTHORIZATION
A user agent that wishes to authenticate itself with a server-- usually,
but not necessarily, after receiving a 401 response--MAY do so by
including an Authorization request-header field with the request. The
Authorization field value consists of credentials containing the
authentication information of the user agent for the realm of the
resource being requested.
request-header
rfc2068
BYTE_RANGES
Since all HTTP entities are represented in HTTP messages as sequences of
bytes, the concept of a byte range is meaningful for any HTTP entity.
(However, not all clients and servers need to support byte- range
operations.)
optional
rfc2068
CACHE_CONTROL
The Cache-Control general-header field is used to specify directives
that MUST be obeyed by all caching mechanisms along the request/response
chain. The directives specify behavior intended to prevent caches from
adversely interfering with the request or response. These directives
typically override the default caching algorithms. Cache directives are
unidirectional in that the presence of a directive in a request does not
imply that the same directive should be given in the response.
general-header
rfc2068
CONNECTION
The Connection general-header field allows the sender to specify options
that are desired for that particular connection and MUST NOT be
communicated by proxies over further connections.
general-header
rfc2068
CONTENT_BASE
The Content-Base entity-header field may be used to specify the base URI
for resolving relative URLs within the entity. This header field is
described as Base in RFC 1808, which is expected to be revised.
entity-header
rfc2068
CONTENT_ENCODING
The Content-Encoding entity-header field is used as a modifier to the
media-type. When present, its value indicates what additional content
codings have been applied to the entity-body, and thus what decoding
mechanisms MUST be applied in order to obtain the media-type referenced
by the Content-Type header field. Content-Encoding is primarily used to
allow a document to be compressed without losing the identity of its
underlying media type.
gzip
entity-header
rfc2068
CONTENT_LANGUAGE
The Content-Language entity-header field describes the natural
language(s) of the intended audience for the enclosed entity. Note that
this may not be equivalent to all the languages used within the
entity-body.
da
entity-header
rfc2068
CONTENT_LENGTH
The Content-Length entity-header field indicates the size of the
message-body, in decimal number of octets, sent to the recipient or, in
the case of the HEAD method, the size of the entity-body that would have
been sent had the request been a GET.
3495
entity-header
rfc2068
CONTENT_LOCATION
The Content-Location entity-header field may be used to supply the
resource location for the entity enclosed in the message.
entity-header
rfc2068
CONTENT_RANGE
The Content-Range entity-header is sent with a partial entity-body to
specify where in the full entity-body the partial body should be
inserted. It also indicates the total size of the full entity-body.
entity-header
rfc2068
CONTENT_RANGE
The Content-Range entity-header is sent with a partial entity-body to
specify where in the full entity-body the partial body should be
inserted. It also indicates the total size of the full entity-body. When
a server returns a partial response to a client, it must describe both
the extent of the range covered by the response, and the length of the
entire entity-body.
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_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 believes the variant was last modified.
Tue, 15 Nov 1994 12:45:26 GMT
entity-header
rfc2068
LOCATION
The Location response-header field is used to redirect the recipient to
a location other than the Request-URI for completion of the request or
identification of a new resource.
response-header
rfc2068
MAX_FORWARDS
The Max-Forwards request-header field may be used with the TRACE method
(section 14.31) to limit the number of proxies or gateways that can
forward the request to the next inbound server. This can be useful when
the client is attempting to trace a request chain which appears to be
failing or looping in mid-chain.
request-header
rfc2068
PRAGMA
The Pragma general-header field is used to include implementation-
specific directives that may apply to any recipient along the
request/response chain.
general-header
rfc2068
PROXY_AUTHENTICATE
The Proxy-Authenticate response-header field MUST be included as part of
a 407 (Proxy Authentication Required) response. The field value consists
of a challenge that indicates the authentication scheme and parameters
applicable to the proxy for this Request-URI.
response-header
rfc2068
PROXY_AUTORIZATION
The Proxy-Authorization request-header field allows the client to
identify itself (or its user) to a proxy which requires authentication.
The Proxy-Authorization field value consists of credentials containing
the authentication information of the user agent for the proxy and/or
realm of the resource being requested.
request-header
rfc2068
PUBLIC
The Public response-header field lists the set of methods supported by
the server. The purpose of this field is strictly to inform the
recipient of the capabilities of the server regarding unusual methods.
response-header
rfc2068
RANGE_RETRIEVAL_REQUESTS
HTTP retrieval requests using conditional or unconditional GET methods
may request one or more sub-ranges of the entity, instead of the entire
entity, using the Range request header, which applies to the entity
returned as the result of the request:
request-header
rfc2068
REFERRER
The Referer[sic] request-header field allows the client to specify, for
the server's benefit, the address (URI) of the resource from which the
Request-URI was obtained (the "referrer", although the header field is
misspelled.)
request-header
rfc2068
SERVER
The Server response-header field contains information about the software
used by the origin server to handle the request. The field can contain
multiple product tokens (section 3.8) and comments identifying the
server and any significant subproducts. The product tokens are listed in
order of their significance for identifying the application.
response-header
rfc2068
TRANSFER_ENCODING
The Transfer-Encoding general-header field indicates what (if any) type
of transformation has been applied to the message body in order to
safely transfer it between the sender and the recipient. This differs
from the Content-Encoding in that the transfer coding is a property of
the message, not of the entity.
general-header
rfc2068
UPGRADE
The Upgrade general-header allows the client to specify what additional
communication protocols it supports and would like to use if the server
finds it appropriate to switch protocols.
HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
general-header
rfc2068
USER_AGENT
The User-Agent request-header field contains information about the user
agent originating the request.
CERN-LineMode/2.15 libwww/2.17b3
request-header
rfc2068
VARY
The Vary response-header field is used by a server to signal that the
response entity was selected from the available representations of the
response using server-driven negotiation (section 12).
response-header
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
|
|
|
|