Nginx-ru mailing list archive (nginx-ru@sysoev.ru)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Re[2]: Ошибка в SSI encoding
- To: nginx-ru@xxxxxxxxx
- Subject: Re: Re[2]: Ошибка в SSI encoding
- From: Andrew Sitnikov <sitnikov@xxxxxxxxxx>
- Date: Thu, 9 Apr 2009 10:14:03 +0300
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=WcpwvbVL3JfNq4i/1pGwsAUo8sGRFTLw492gU+G7iBc=; b=SkW1kBDLulGKYG3IB9SXU60bXaeSLw+r9KaytUSfN8+CdILqtO27UgQ51jy8SCVhzw csN28woue1kEko8lcR0ea5VVphlqPi7FOfPPnE22RA7Djv7DpOQ5M3b6vFmYII6Ek2QY d/gt9P3cq6DXe5cWtOmyhzltodT7GyrRaJITw=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=Dj4MExXVe6FuWjGeR2LCankLDFdtwhPov6Gb94cnzQ01OaWeSKuO9i1bHwDw1kLZ1M r/1jsdpcxODmZ+Pz2BPbUKCoO2A8NrwZZgAKXq0fPLSliqr2Djt8jX4Yqu1gMNABVit2 vFyF+W4U5jPtuRCE2vxsc2I6wi75vEf5friL4=
- In-reply-to: <E1Lrnda-0005nO-00.ilvin-mail-ru@xxxxxxxxxxx>
- References: <3af8048a0904080805s67c8a9d8x3e78ee7eaefb4f85@xxxxxxxxxxxxxx> <E1Lrnda-0005nO-00.ilvin-mail-ru@xxxxxxxxxxx>
> Это регулируется уже не RFC1738.
указанный вами RFC разделители для searchpart тоже не регулирует.
The HTTP protocol is specified elsewhere. This specification only
describes the syntax of HTTP URLs.
An HTTP URL takes the form:
http://<host>:<port>/<path>?<searchpart>
where <host> and <port> are as described in Section 3.1. If :<port>
is omitted, the port defaults to 80. No user name or password is
allowed. <path> is an HTTP selector, and <searchpart> is a query
string. The <path> is optional, as is the <searchpart> and its
preceding "?". If neither <path> nor <searchpart> is present, the "/"
may also be omitted.
Within the <path> and <searchpart> components, "/", ";", "?" are
reserved. The "/" character may be used within HTTP to designate a
hierarchical structure.
|
