Re: HTML encoding in URLs
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 14155
interpreted = N
texte = >The problem is (as stated in OmniWeb's post below) that URLs should be HTML-encoded, not ASCII. In other words, if something like &ne appears ANYWHERE in a HTML page, including inside the get string of a URL, it should be interpreted as ‚ (ie not equals). In other words, the following URL > >
search > >should be interpreted as > >
searchWe ran into this with an early WebCatalog that used &gr, which we changed to > for exactly this reason (Netscape tweaked it to >). We feel it is somewhat improper for a browser to convert unterminated (not followed by ;) escape strings.Here's a couple of workarounds:1) Use form method=POST instead of HREF hyperlinks 2) (probably the best) Use embedded [Search] contexts so that you never have to pass the &neWHATEVER text in a hyperlink. Instead, just pass the comparison text in a form variable, and embed [Search db=xx&neb=[VARIABLE]] right into your template. 3) Use WebCatalog's [browsername] tag to let you know when someone is using OmniWeb, and ask them to change their preferences for unterminated escape sequences.Grant Hulbert, V.P. Engineering | ==== eCommerce for the Rest of Us ==== Pacific Coast Software | WebCatalog, WebMerchant 11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster San Diego, CA 92128 | SiteGuard 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com
Associated Messages, from the most recent to the oldest:
>The problem is (as stated in OmniWeb's post below) that URLs should be HTML-encoded, not ASCII. In other words, if something like &ne appears ANYWHERE in a HTML page, including inside the get string of a URL, it should be interpreted as ‚ (ie not equals). In other words, the following URL > >
search > >should be interpreted as > >
searchWe ran into this with an early WebCatalog that used &gr, which we changed to > for exactly this reason (Netscape tweaked it to >). We feel it is somewhat improper for a browser to convert unterminated (not followed by ;) escape strings.Here's a couple of workarounds:1) Use form method=POST instead of HREF hyperlinks 2) (probably the best) Use embedded
[search] contexts so that you never have to pass the &neWHATEVER text in a hyperlink. Instead, just pass the comparison text in a form variable, and embed [Search db=xx&neb=[VARIABLE]] right into your template. 3) Use WebCatalog's
[browsername] tag to let you know when someone is using OmniWeb, and ask them to change their preferences for unterminated escape sequences.Grant Hulbert, V.P. Engineering | ==== eCommerce for the Rest of Us ==== Pacific Coast Software | WebCatalog, WebMerchant 11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster San Diego, CA 92128 | SiteGuard 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com
Grant Hulbert
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
[WebDNA] checking for mixed case text (2009)
[WebDNA] agree? --> [url] broken inside [redirect], on a square-bracket-style include, included from a XML-style page (2009)
[WebDNA] DigitalOcean Snapshots (2019)
unusual search problem (1998)
grep question - how to strip spaces from the beginning ofa string? (2002)
$flushdatabases question ... (1998)
Date math format (1998)
Was 5.0 Pricing, now Sandbox versus Website and ruminating (2003)
Emailer (WebCat2) (1997)
Show if file exists (2004)
WebTen and WebCat (1997)
Canada oh Canada (2004)
Kaaaaahhhhhhhnnnnnnn! (1997)
[WebDNA] CRC-16-CCITT (2008)
Trouble with formula.db + more explanation (1997)
FYI: SmithMicro Financial Report (2000)
[WebDNA] Apache 2 httpd.conf Question (2008)
WCS Newbie question (1997)
Undeclared variables (2004)
[WebDNA] Store module/site (2012)