On Mon, 29 Nov 1999, Robin Berjon wrote:
> I'm unsure that even parsing the request will get you
> that. A grep through my logs shows no trace of the
> fragment ever being present, while a lot of pages
> containing some appear. It wouldn't surprise me totally
> if the browser kept the fragment to
At 10:04 29/11/1999 -0800, brian moseley wrote:
>it appears that neither $r->uri nor $r->parsed_uri retain
>any knowledge of the fragment.
>
>is there any way for me to retrieve the fragment info short
>of parsing $r->the_request?
I'm unsure that even parsing the request will get you that. A grep
> "Andrei" == Andrei A Voropaev <[EMAIL PROTECTED]> writes:
Andrei> Correct too. Though Apache::URI::fragment() is present and
Andrei> even documented :) Probably because some browsers pass this
Andrei> fragment to the server?
No, because a server could pass *back* a URI with a fragment in
g
Correct too. Though Apache::URI::fragment() is present and even documented :)
Probably because some browsers pass this fragment to the server?
Andrei
On Mon, Nov 29, 1999 at 10:16:04AM -0800, Randal L. Schwartz wrote:
> > "brian" == brian moseley <[EMAIL PROTECTED]> writes:
>
> brian> im re
I've had the same problem. There's a mistake in the Eagle book when it
states that $r->the_request() eq join(' ', $r->method, $r->uri,
$r->protocol).
Proper way to access fragment as well as query_string is to use
my $uri = $r->parsed_uri();
my $fragment = $uri->fragment();
Andrei
On Mon, Nov 2
> "brian" == brian moseley <[EMAIL PROTECTED]> writes:
brian> im requesting the url
brian> http://www.maz.org/foo/index.html#perl
brian> it appears that neither $r->uri nor $r->parsed_uri retain
brian> any knowledge of the fragment. they both return
brian> /foo/index.html
brian> is th
maybe $r->path_info is what you are after?
--Geoff
> -Original Message-
> From: brian moseley [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, November 29, 1999 1:04 PM
> To: [EMAIL PROTECTED]
> Subject: fragment in $r->uri
>
>
> im requesting the url
im requesting the url
http://www.maz.org/foo/index.html#perl
it appears that neither $r->uri nor $r->parsed_uri retain
any knowledge of the fragment. they both return
/foo/index.html
is there any way for me to retrieve the fragment info short
of parsing $r->the_request?
