Name anchor

[Chris Kennedy]

I am passing a querystring e.g.
http://office.cybase.co.uk/placeadvert/addimages.asp?maximage=3&officeid=118#subimages

I want to use a named anchor. but this confuses my asp as it thinks officeid
is 118#subimages not 118

 

[Patrice]

Believe it or not I don't remember to have use bot anchor names and
parameters ???!!

My first though would be that anchor name should be after the page name, not
after the parameters. You may want to quick check this in a spec but I'm
fairly sure of that...

Patrice

 

[McKirahan]

I am passing a querystring e.g.
http://office.cybase.co.uk/placeadvert/addimages.asp?maximage=3&officeid=118
#subimages

I want to use a named anchor. but this confuses my asp as it thinks officeid
is 118#subimages not 118

A Google on "querystring named anchor" found:

http://www.webmasterworld.com/forum21/8405.htm

Which includes the following:

Section 4 in RFC 2396 (http://www.ietf.org/rfc/rfc2396.txt) clearly states:

"The term "URI-reference" is used here to denote the common usage of a
resource identifier. A URI reference may be absolute or relative,
and may have additional information attached in the form of a
fragment identifier. However, "the URI" that results from such a
reference includes only the absolute URI after the fragment
identifier (if any) is removed and after any relative URI is resolved
to its absolute form."

In other words, according to the RCF the URL is split by the fragment
identifier first (#), if present, and *then* parsed as an address.
It's therefore imperative that the fragment identifier is placed last in the
URL, which may also be combined with a query string as in:

 

[Steven Burn]

The anchor name is usually stored at the end of the URL, for example;

http://freeware.it-mate.co.uk/?Cat=Security#135

If the query is getting mixed up I'd personally be inclined to blame the way the querystring is being extracted.

--
Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk

Keeping it FREE!

 

[Patrice]

Oh... Interesting. so you have to handle this yourself... ins't it something
that the QueryString property should do ? I'll try to see how it behaves in
ASP.NET...

Patrice

--

"Steven Burn" <[email protected]> a écrit dans le message de
The anchor name is usually stored at the end of the URL, for example;

http://freeware.it-mate.co.uk/?Cat=Security#135

If the query is getting mixed up I'd personally be inclined to blame the way
the querystring is being extracted.

--
Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk

Keeping it FREE!

 

[Steven Burn]

For the example I gave, I am simply using;

sTemp = LCase(Request.Querystring("Cat"))

This works just fine for me, and the anchor works without any problems.

--
Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk

Keeping it FREE!

 

[Patrice]

Ah yes. Actually Chris just said it wasn't working but doesn't show his
code. Perhaps he uses just Request.QueryString ?

Patrice

--

"Steven Burn" <[email protected]> a écrit dans le message de
For the example I gave, I am simply using;

sTemp = LCase(Request.Querystring("Cat"))

This works just fine for me, and the anchor works without any problems.

--
Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk

Keeping it FREE!

 

[Steven Burn]

Thats what I was thinking too......

--
Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk

Keeping it FREE!