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:
form data submission gets truncated (1997)
[BULK] [WebDNA] [BULK] [middle] behavior (2020)
Code to convert relative to absolute URLs in HTML files (2004)
Comparing two fields so the match (1998)
[/application] error? (1997)
Umm...about those log files? (Off Topic) (1997)
Introduction/Tutorial/QuickStart (1997)
Great product and great job ! (1997)
Reversed words (1997)
Cookies (1999)
WebCat2b13MacPlugIn - syntax to convert date (1997)
SiteGuard Admin Feature ? (1997)
$append (1998)
PCS Emailer's role ? (1997)
vs (1997)
ShowNext (1997)
Narrowing NT Crashing error (2000)
Snake Bites (1997)
listcookies works only sometimes (1997)
Download Question (1997)