On 30/10/06, Ivo F.A.C. Fokkema <I.F.A.C.Fokkema@xxxxxxx> wrote:
On Sun, 29 Oct 2006 23:40:47 -0600, Richard Lynch wrote:
> On Fri, October 27, 2006 4:53 pm, Børge Holen wrote:
>> On Friday 27 October 2006 19:34, Richard Lynch wrote:
>>> And the header("Location: ...") requires a full URL.
>>
>> No it doesn't. but he's missing an ' at first glance
>
> Yes, it does:
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.30
>
> Note the use of 'absolute' within that section.
Although I always use a full URL as well, doesn't absolute just mean
non-relative? As in:
Location: /Protocols/rfc2616/rfc2616-sec14.html#sec14.30
(absolute URI)
Location: ./rfc2616-sec14.html#sec14.30
(relative URI)
If you need contextual information to make sense of the URI (such as
the server name from a previous request) then it's not absolute.
RFC 2396: Uniform Resource Identifiers
"An absolute identifier refers to a resource independent of the
context in which the identifier is used. In contrast, a relative
identifier refers to a resource by describing the difference within a
hierarchical namespace between the current context and an absolute
identifier of the resource."
-robin
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
