On Tue, 2006-10-31 at 11:58 +0100, Robin Vickery wrote:
> On 30/10/06, Robert Cummings <robert@xxxxxxxxxxxxx> wrote:
> > On Mon, 2006-10-30 at 12:28 +0100, Robin Vickery wrote:
> > > 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."
> >
> > Please note you are quoting from an RFC with the following title:
> >
> > Uniform Resource Identifiers (URI): Generic Syntax
> >
> > Pay special attention to "Generic Syntax" in the title.
> >
> > The RFC linked by Richard clearly indicates that for the Location
> > response-header that "the field value consists of a single absolute
> > URI". This currently has the final word for the Location response-header
> > and therefore is the standard.
>
> What?
>
> Pay special attention to what I wrote.
Seems a bit ambiguous :)
> I wasn't disagreeing with Richard, or the RFC he quoted. The OP
> expressed some confusion about what comprised an 'absolute URI' so I
> quoted the section of the RFC that defined an 'absolute URI'.
>
> There's no question that a Location header should contain an absolute
> URI as its value.
Cheers,
Rob.
--
.------------------------------------------------------------.
| InterJinn Application Framework - http://www.interjinn.com |
:------------------------------------------------------------:
| An application and templating framework for PHP. Boasting |
| a powerful, scalable system for accessing system services |
| such as forms, properties, sessions, and caches. InterJinn |
| also provides an extremely flexible architecture for |
| creating re-usable components quickly and easily. |
`------------------------------------------------------------'
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
