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:
Checking Webdna is running (2007)
Dark Horse Comics success story (1997)
Modifying Carts (1999)
NT or Mac (1998)
Truncated value after space - refresh my memory.... (1997)
Can ShowNext do this? (2000)
Where's Cart Created ? (1997)
Re:Searching for ALL / empty form field (1997)
WebCat2 Append problem (B14Macacgi) (1997)
Fwd: Problems with Webcatalog Plug-in (1997)
UPS (2003)
SSL (1998)
Pass a form (2003)
form image (2000)
randomness (1997)
4.0x on production server (2000)
NT Manual (1997)
WebCatalog for guestbook ? (1997)
[WebDNA] Client wants backup copy of site (2010)
Mac & Internet Explorer (2000)