|
In case anybody else runs into this: %26 would work from the browser perspective (in that it resolved to the correct name) but would not work for the database being called.
Normally ampersands (the & character) are used to separate different variables when a list of them is being sent to a web application. You'd use %26 to tell the application NOT to treat it as a separator (which isn't what you want to do, here.)
The problem with ampersand itself was happening because Microsoft Command Interpreter was taking the start command and trying to start a new command with each ampersand shown.
Exactly. It wasn't the web server causing the problem, it was the command interpreter, so inserting %26 (or worse, &), doesn't make sense.
The solution is to tell the command interpreter to ignore normal processing of the ampersand by using a caret in front of it: "start http://servername/csesc/csoe?cmd=CUSTOM_INT^&pid=CV_KT^&uid=admin^&qty=2";
Hmmm... I had no idea that the caret character worked for this. That might be good to know some day.
Another solution is to put quotes around the data portion of the URL. For example:
start http:"//servername/csesc/csoe?cmd=CUSTOM_INT&pid=CV_KT&uid=admin"You have to leave the http: part out of the quoted string, or it won't know that you want to launch a browser. It's kinda weird.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
