|
> Try replacing "&" with "%26" in your URL 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. The database on the back end was not substituting "&" for "%26" while the browser would. Related to this there are a ton of sites explaining why ampersands are not good characters to put into URLs, especially when trying to pass parameters to back end databases..... 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. "start http://servername/csesc/csoe?cmd=CUSTOM_INT&pid=CV_KT&uid=admin&qty=2" was being interpreted like a batch file with "start http://servername/csesc/csoe?cmd=CUSTOM_INT" "pid=CV_KT" "uid=admin" "qty=2". 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" works.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.