>>If you want to include, say, a copyright symbol in a submit button, how
would you do that without using the appropriate character entity in the
VALUE attribute of the button?
Then I will use an HTML string, since I know the value is to be finally
used and displayed as an HTML string.
But if I
> Ok, but in HTML, there is no entity inside an attribute,
> (unless you decide to pass an HTML string in the attribute).
If you want to include, say, a copyright symbol in a submit button, how
would you do that without using the appropriate character entity in the
VALUE attribute of the button?
>>That's simply not going to happen. The ampersand is the character used to
mark the start of an entity.
Ok, but in HTML, there is no entity inside an attribute, (unless you
decide to pass an HTML string in the attribute).
>>Changing this would require changing every XML parser in existence.
> I understand this whole debate on escaping ampersands but
> it's almost too late to even worry about them. ?a=1&b=2 has
> been in use way before I got into programming. Now that it's
> in such wide use, this standard should be reversed. & should
> be reconsidered for xml and not the other way
On 4/17/07, Dave Watts <[EMAIL PROTECTED]> wrote:
>
> > Ok, I see now. But it applies to XHTML, not standard HTML
>
> We recommend that HTTP server implementors, and in particular, CGI
> implementors support the use of ";" in place of "&" to save authors the
> trouble of escaping "&" characters in
> Ok, I see now. But it applies to XHTML, not standard HTML
If you read the quote carefully, it refers to common mishandling of
ampersands within URIs in HTML user agents. But anyway, here's the relevant
quote from the HTML 4.01 spec:
http://www.w3.org/TR/html401/appendix/notes.html#h-B.2.2
"B.
>>You can also set up some rewrite rules with Apache's mod_rewrite or
one of the IIS filters.
Which IIS filter?
I can see about ISAPI filters in IIS, but where are they?
Do I have to develop my own ?
--
___
REUSE CODE! Use custom tags;
See http://www.content
>>Did everyone miss the function that I posted earlier that fixes the
problem?
No, I've seen it and eventually going to implement it.
For the moment I'm trying to implement a filter on IIS server as
suggested by Russ, but
it does not look trivial ;-)
--
___
> >>For what it's worth, I've seen similar behaviour from
> certain search engines, where links have ampersands in them.
>
> That's the case: the make an url to their own site, passing
> the result link as a parameter.
> In the process they escape all characters, which they should not do.
>
>
>>You can also set up some rewrite rules with Apache's mod_rewrite or
one of
the IIS filters.
Ah good idea, I'll see what I can do.
--
___
REUSE CODE! Use custom tags;
See http://www.contentbox.com/claude/customtags/tagstore.cfm
(Please send any spam to this
>>it discusses the HREF attribute of an element.
Ok, I see now. But it applies to XHTML, not standard HTML
Anyway, this is obviously in contradiction with RFC 1738.
In HTML, what's inside an attribute is NOT HTML, it is just a string value.
Of course, one can pass a string contaning HTML in a pa
> To: CF-Talk
> Subject: Re: Who is wrong ?
>
> >>For what it's worth, I've seen similar behaviour from certain search
> engines, where links have ampersands in them.
>
> That's the case: the make an url to their own site, passing the result
> link as a pa
>>For what it's worth, I've seen similar behaviour from certain search
engines, where links have ampersands in them.
That's the case: the make an url to their own site, passing the result
link as a parameter.
In the process they escape all characters, which they should not do.
>> It's trivial
We're not talking about documents here, we're talking about URLs,
which don't conform to HTML or XML specifications. URLs embedded
inside an HTML/XML document must conform to the spec, and therefore
have entity-escaped ampersands, but URLs themselves have literla
(unescaped) ampersands.
For what
> Well, this is true for HTML, but here we are inside a url address.
> You're not supposed to pass HTML in a url address, aren't you ?
Presumably, that URL is contained within an HTML page. Most of the links I
click are actually within HTML pages. I can't speak for your experience,
though.
> The
furthermore, one can read in http://www.ietf.org/rfc/rfc1738.txt :
"Many URL schemes reserve certain characters for a special meaning:
their appearance in the
scheme-specific part of the URL has a designated semantics. If the
character corresponding
to an octet is reserved in a scheme, the
>>"n both SGML and XML, the ampersand character ("&") declares the
beginning
of an entity reference (e.g., ® for the registered trademark symbol
"(r)").
Well, this is true for HTML, but here we are inside a url address.
You're not supposed to pass HTML in a url address, aren't you ?
The document
The problem with escaping ampersands is that old browsers don't convert them
back to the & character when sending them back to the server...
I have a little piece of code that I run on every request to fix the
urlvars... It looks something like this...
RL.id and URL.cat.
Rob
-Original Message-
From: Dave Watts [mailto:[EMAIL PROTECTED]
Sent: 17 April 2007 10:35
To: CF-Talk
Subject: RE: Who is wrong ?
> URLs should contain unescaped ampersands. This URL:
>
>.../index.cfm?id=3&cat=dusty
>
> defines two params, o
Can I ask why the asterix is there?
index.cfm?p=page*&id*=12
~|
ColdFusion MX7 by Adobe®
Dyncamically transform webcontent into Adobe PDF with new ColdFusion MX7.
Free Trial. http://www.adobe.com/products/coldfusion?sdid=RVJV
> URLs should contain unescaped ampersands. This URL:
>
>.../index.cfm?id=3&cat=dusty
>
> defines two params, one named 'id, and one named 'amp;cat',
> with values you can surmise.
Actually, I think that's incorrect:
http://www.w3.org/TR/xhtml1/#C_12
"n both SGML and XML, the ampersand c
?p=page&id=12,
> but actually calls index.cfm?p=page*&*id=12 in the HTTP request.
>
> Who is wrong?
> Should I encode the parameters differently in the url?
>
> --
> ___
> REUSE CODE! Use custom tags;
> See http://www.conte
d=12,
but actually calls index.cfm?p=page*&*id=12 in the HTTP request.
Who is wrong?
Should I encode the parameters differently in the url?
--
___
REUSE CODE! Use custom tags;
See http://www.contentbox.com/claude/customtags/tagstore.cfm
(Please send an
23 matches
Mail list logo
