> Yeah... in cflocation... what a bummer hmmmm -- would this be 
> a bug then??

Nope.  Using cflocation doesn't output HTML so it's not subject to the
compliancy etc that you seek.  That tag uses the "Location" header of
the HTTP protocol to tell the client that "these aren't the droids
yo..." *cough* sorry, "the file you're looking for isn't here - try HERE
instead" (in fact CF sends a "moved temporarily" status too, HTTP status
code 302 which tells the browser to go to the location specified in the
Location header).

If you click on a link which has & in it the page requested is
actually using & not & (e.g. index.cfm?thing=wotsit&other=thing
=> index.cfm?thing=wotsit&other=thing)

So in conclusion, use & for outputed HTML link and & for cflocation
calls.

Ta.

Tim.

-------------------------------------------------------
RAWNET LTD - Internet, New Media and ebusiness Gurus.
Visit our new website at http://www.rawnet.com for
more information about our company, or call us free
anytime on 0800 294 24 24.
-------------------------------------------------------
Tim Blair
Web Application Engineer, Rawnet Limited
Direct Phone : +44 (0) 1344 393 441
Switchboard : +44 (0) 1344 393 040
-------------------------------------------------------
This message may contain information which is legally
privileged and/or confidential.  If you are not the
intended recipient, you are hereby notified that any
unauthorised disclosure, copying, distribution or use
of this information is strictly prohibited. Such
notification notwithstanding, any comments, opinions,
information or conclusions expressed in this message
are those of the originator, not of rawnet limited,
unless otherwise explicitly and independently indicated
by an authorised representative of rawnet limited.
-------------------------------------------------------



-- 
** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For human help, e-mail: [EMAIL PROTECTED]

Reply via email to