[cfaussie] Re: CGI.QUERY_STRING

[Ayudh Nagara]

Steve, that can't be right. I've used CGI_QUERY_STRING with no problems with all URL parameters returned completely. The query string you quoted should work fine. Must be something else causing the problem.   Having said that, the ampersand in the query string can cause problems. I had a bug some time ago which had me scratching my head for hours. If you use the following URL: http://www.mysite.com?param1=123&param2=456 and you display #CGI.QUERY_STRING# in your page output, you'll see: param1=123*m2=456 (where * is the paragraph control character) Eventually I figured out that the browser was interpreting "&para" as a paragraph marker.   Regards: Ayudh   +--------------------------------------------------------------+ | Turn on your Revenue Stream...                               | | Bolt on a Virtual Cash Register to your e-commerce site now. | | VeriPay from Xilo Online: http://www.xilo.com                | +--------------------------------------------------------------+ ----- Original Message ----- From: [EMAIL PROTECTED] To: CFAussie Mailing List Sent: Monday, February 24, 2003 14:30 Subject: [cfaussie] CGI.QUERY_STRING Hi,   It seems that cgi.query_string only returns the first url variable name and value from a url regardless of how many other variables exist in the url.   eg. cgi.query_string returns only "studcode=123456" from the following url:   http://www.myurl.com/somepage.cfm?studcode=123456&area=23&allowance=69   is there another cgi var i am missing that will return "studcode=123456&area=23&allowance=69"? or do i need to check for a len(cgi.query_string) and return everything after the question mark?   thanks.... steve c --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MX Downunder AsiaPac DevCon - http://mxdu.com/