Re: How do I specify a & character in Grep?
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 34133
interpreted = N
texte = >http://www.domain.com/firstfolder/secondfolder/filename.html?blah=1&?blah2=2This is not a proper URL -- it contains more than one question mark. A single question mark is the delimiter between the path and the parameters. So it's possible to parse a normal URL apart without needing grep.>My question still stands. I want to know if the Grep tag is not >true regex or is there a way to identify and use & in the grep >expressions. > >It shouldn't be called grep if you can't do real regex stuff in it. >Maybe it should be called Grep is a good name for marketing >purposes but it isn't really the same.Chill, dude, this is not a conspiracy, it's just a simple syntax question. The answer was already presented with the use of the [url] context: embedded ampersands and other special characters in URLs are represented as their HEX-escaped equivalents. In the case of ampersand, the equivalent code is %26. You can automate this by wrapping [url]...[/url] around any text which needs to be passed as a parameter to *any* WebDNA context, not just grep.The general solution to any problem like this is to wrap every parameter inside [url]:[grep search=[url]...some text here which may contain ampersand...[/url]&replace=[url]...[/url]]...[/grep]This ensures that any 'special' characters get passed thru without modification or misinterpretation. Ampersands as delimiters was not our invention: it's how browsers send URLs to servers, and we purposely chose it so as to keep things consistent for web programmers who are already accustomed to URLs.Technical Support ********************************** Smith Micro, Internet Solutions Div | eCommerce (WebCatalog) 16855 West Bernardo Drive, #380 | ------------------------- San Diego, CA 92127 | Software & Site Development WebCatalog Support: (858) 675-0632 | http://www.smithmicro.com Fax: (858) 675-0372 **********************************------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
>http://www.domain.com/firstfolder/secondfolder/filename.html?blah=1&?blah2=2This is not a proper URL -- it contains more than one question mark. A single question mark is the delimiter between the path and the parameters. So it's possible to parse a normal URL apart without needing grep.>My question still stands. I want to know if the Grep tag is not >true regex or is there a way to identify and use & in the grep >expressions. > >It shouldn't be called grep if you can't do real regex stuff in it. >Maybe it should be called Grep is a good name for marketing >purposes but it isn't really the same.Chill, dude, this is not a conspiracy, it's just a simple syntax question. The answer was already presented with the use of the [url] context: embedded ampersands and other special characters in URLs are represented as their HEX-escaped equivalents. In the case of ampersand, the equivalent code is %26. You can automate this by wrapping [url]...[/url] around any text which needs to be passed as a parameter to *any* WebDNA context, not just grep.The general solution to any problem like this is to wrap every parameter inside [url]:[grep search=[url]...some text here which may contain ampersand...[/url]&replace=[url]...[/url]]...[/grep]This ensures that any 'special' characters get passed thru without modification or misinterpretation. Ampersands as delimiters was not our invention: it's how browsers send URLs to servers, and we purposely chose it so as to keep things consistent for web programmers who are already accustomed to URLs.Technical Support ********************************** Smith Micro, Internet Solutions Div | eCommerce (WebCatalog) 16855 West Bernardo Drive, #380 | ------------------------- San Diego, CA 92127 | Software & Site Development WebCatalog Support: (858) 675-0632 | http://www.smithmicro.com Fax: (858) 675-0372 **********************************------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
WebDNA Support
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:
webcat in the subject line - SMSI (2002)
[ot] Securing PHP & MySQL (2003)
Searching Multiple DBs (1997)
Aaron Kant do contextses (2000)
Format of Required fields error message (1997)
[WebDNA] Simple Date Format Conversion (2008)
Reading through the Order File (1999)
Macos8.6 to X migration problems (2000)
[url] (1997)
Limitations on fields? Server is crashing (1997)
problem serving foreign languages text (1997)
Error Log with Linux? (2000)
Setting up shop (1997)
FYI: virus alert (1996)
WebCatalog2 Feature Feedback (1996)
WC 2.0 frames feature (1997)
[WebDNA] webdna in amazon (2020)
Weird happenings (1998)
Mac Vs WindowsNT (1997)
WebCat2 - Getting to the browser's username/password data (1997)