HTTP redirect

"ghhou" <[email protected]> Fri, 28 Nov 2003 18:29:45 +0800
Newsgroups	gmane.comp.mobile.kannel.devel
Message-ID	<[email protected]>
Rene Kluwen,

But 'location' can only appear in the response '201' and '3**'.
'Content-location' can appear in most response.

Best Regards,
Guanghua Hou
----- Original Message -----
From: "Rene Kluwen" <[email protected]>
To: "ghhou" <[email protected]>; "Stipe Tolj" <[email protected]>;
<[email protected]>
Sent: Friday, November 28, 2003 6:23 PM
Subject: RE: HTTP redirect


> Content-Location is a http level equivalent of the base tag. But also not
widely used.
> Why not just take the Location header of the previous response?
>
> Rene Kluwen
> Chimit
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]On Behalf Of
> ghhou
> Sent: vrijdag 28 november 2003 2:21
> To: [email protected]; Stipe Tolj; [email protected]
> Subject: Fw: HTTP redirect
>
>
> Rene Kluwen,
>
> In HTTP1.0, "Content-base" is base URI. But HTTP1.1 doesn't support this
> header.
>
> Can 'content-location' in the http response be used as base URL?  Rfc2616
> says "The value of Content-Location also defines the base URI for the
> entity.".
>
>
> Best Regards,
> Guanghua Hou
> ----- Original Message -----
> From: "Rene Kluwen" <[email protected]>
> To: "ghhou" <[email protected]>; "Stipe Tolj" <[email protected]>;
> <[email protected]>
> Sent: Thursday, November 27, 2003 10:39 PM
> Subject: RE: HTTP redirect
>
>
> > BASE tags in HTML documents are rarely used.
> > Most HTML documents go without.
> >
> > Rene Kluwen
> > Chimit
> >
> > -----Original Message-----
> > From: [email protected] [mailto:[email protected]]On Behalf Of
> > ghhou
> > Sent: donderdag 27 november 2003 4:43
> > To: Stipe Tolj; [email protected]
> > Cc: [email protected]
> > Subject: HTTP redirect
> >
> >
> > Stipe,
> >
> > The Base element in HTML specifies an absolute URI that acts as the base
> URI
> > for resolving relative URIs.
> > For example, given the following BASE declaration and A declaration:
> >
> >     <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
> >     "http://www.w3.org/TR/html4/strict.dtd">
> >     <HTML>
> >     <HEAD>
> >     <TITLE>Our Products</TITLE>
> >     <BASE href="http://www.aviary.com/products/intro.html">
> >     </HEAD>
> >     <BODY>
> >     <P>Have you seen our <A href="../cages/birds.gif">Bird Cages</A>?
> >     </BODY>
> >     </HTML>
> >
> >     the relative URI "../cages/birds.gif" would resolve to:
> >     http://www.aviary.com/cages/birds.gif
> >
> > I'm sure you may be clear about the problem in proxy redirection. If no
> base
> > element existing, problem will happen.
> >
> > Best Regards,
> > Guanghua Hou
> > ----- Original Message -----
> > From: "Stipe Tolj" <[email protected]>
> > To: "Rene Kluwen" <[email protected]>
> > Cc: "ghhou" <[email protected]>; <[email protected]>
> > Sent: Thursday, November 27, 2003 8:20 AM
> > Subject: Re: HTTP redirect
> >
> >
> > > Rene Kluwen wrote:
> > > >
> > > > -----BEGIN PGP SIGNED MESSAGE-----
> > > > Hash: SHA1
> > > >
> > > > If you mean a relative URL in the Location: header.
> > > > Then this is something against HTTP specs. One should not use them.
> > > > Even though almost all browsers do prepend the original http-path if
> you
> > do
> > > > send them.
> > >
> > > nop, the point is different.
> > >
> > > Kannel wapbox does the Location following (hence redirection)
> > > transparently to the WAP user agent. Hence relative URLs within the
> > > WAP deck would result to address resources that are ment to be on a
> > > previously redirected URL. And there is where we "may" run into
> > > problems.
> > >
> > > Stipe
> > >
> > > mailto:[email protected]
> > > -------------------------------------------------------------------
> > > Wapme Systems AG
> >
> >
> >
>
>