RE: Request parameter value containing = is not parsed well
Howdy, I don't know (and don't really care much about at this point) 4.0.4, but I can't reproduce what you claim on 4.1.27. The behavior is correct with equal signs in param value, they are retained. Yoav Shapira Millennium ChemInformatics -Original Message- From: Vijay Kandy [mailto:[EMAIL PROTECTED] Sent: Friday, August 15, 2003 11:41 AM To: 'Tomcat Users List' Subject: Request parameter value containing = is not parsed well Hello All, I have a servlet whose expected parameter is ZAZBZ and its value is CZlYnXtAIBDC=D9W7V So calling http://host/context/name?ZAZBZ=CZlYnXtAIBDC=D9W7V would cause System.out.println(request.getParameter(ZAZBZ)); to print CZlYnXtAIBDC=D9W7V in Tomcat 3.2.3. But in tomcat 4.0.4 the printout is CZlYnXtAIBDC The results are the same when the URL is encoded because = remains the same. Looks like parameter value cannot contain = Please let me know if I am missing something. Sincerely, Vijay - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Request parameter value containing = is not parsed well
Hi = encoded is %3D, so that's where you are missing something I think. greetz Hans At 10:41 15/08/2003 -0500, Vijay Kandy wrote: Hello All, I have a servlet whose expected parameter is ZAZBZ and its value is CZlYnXtAIBDC=D9W7V So calling http://host/context/name?ZAZBZ=CZlYnXtAIBDC=D9W7V would cause System.out.println(request.getParameter(ZAZBZ)); to print CZlYnXtAIBDC=D9W7V in Tomcat 3.2.3. But in tomcat 4.0.4 the printout is CZlYnXtAIBDC The results are the same when the URL is encoded because = remains the same. Looks like parameter value cannot contain = Please let me know if I am missing something. Sincerely, Vijay - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Request parameter value containing = is not parsed well
Thank you for your testing. So did you URLEncode the param value? Is there a trick not to URLEncode and still retain the value. Because was alright on 3.2.3. Sincerely, vijay Howdy, I don't know (and don't really care much about at this point) 4.0.4, but I can't reproduce what you claim on 4.1.27. The behavior is correct with equal signs in param value, they are retained. Yoav Shapira Millennium ChemInformatics -Original Message- From: Vijay Kandy [mailto:[EMAIL PROTECTED] Sent: Friday, August 15, 2003 11:41 AM To: 'Tomcat Users List' Subject: Request parameter value containing = is not parsed well Hello All, I have a servlet whose expected parameter is ZAZBZ and its value is CZlYnXtAIBDC=D9W7V So calling http://host/context/name?ZAZBZ=CZlYnXtAIBDC=D9W7V would cause System.out.println(request.getParameter(ZAZBZ)); to print CZlYnXtAIBDC=D9W7V in Tomcat 3.2.3. But in tomcat 4.0.4 the printout is CZlYnXtAIBDC The results are the same when the URL is encoded because = remains the same. Looks like parameter value cannot contain = Please let me know if I am missing something. Sincerely, Vijay - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Request parameter value containing = is not parsed well
You are right. That's where I have an issue. Thank you. Vijay -Original Message- From: Hans Wichman [mailto:[EMAIL PROTECTED] Sent: Friday, August 15, 2003 11:10 AM To: Tomcat Users List; 'Tomcat Users List' Subject: Re: Request parameter value containing = is not parsed well Hi = encoded is %3D, so that's where you are missing something I think. greetz Hans At 10:41 15/08/2003 -0500, Vijay Kandy wrote: Hello All, I have a servlet whose expected parameter is ZAZBZ and its value is CZlYnXtAIBDC=D9W7V So calling http://host/context/name?ZAZBZ=CZlYnXtAIBDC=D9W7V would cause System.out.println(request.getParameter(ZAZBZ)); to print CZlYnXtAIBDC=D9W7V in Tomcat 3.2.3. But in tomcat 4.0.4 the printout is CZlYnXtAIBDC The results are the same when the URL is encoded because = remains the same. Looks like parameter value cannot contain = Please let me know if I am missing something. Sincerely, Vijay - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Request parameter value containing = is not parsed well
Howdy, I didn't even URLEncode the param value, I simply entered it into the browser's address bar, and the servlet just does request.getParameter(paramName). No encoding or decoding. Yoav Shapira Millennium ChemInformatics -Original Message- From: Vijay Kandy [mailto:[EMAIL PROTECTED] Sent: Friday, August 15, 2003 12:37 PM To: 'Tomcat Users List' Subject: RE: Request parameter value containing = is not parsed well Thank you for your testing. So did you URLEncode the param value? Is there a trick not to URLEncode and still retain the value. Because was alright on 3.2.3. Sincerely, vijay Howdy, I don't know (and don't really care much about at this point) 4.0.4, but I can't reproduce what you claim on 4.1.27. The behavior is correct with equal signs in param value, they are retained. Yoav Shapira Millennium ChemInformatics -Original Message- From: Vijay Kandy [mailto:[EMAIL PROTECTED] Sent: Friday, August 15, 2003 11:41 AM To: 'Tomcat Users List' Subject: Request parameter value containing = is not parsed well Hello All, I have a servlet whose expected parameter is ZAZBZ and its value is CZlYnXtAIBDC=D9W7V So calling http://host/context/name?ZAZBZ=CZlYnXtAIBDC=D9W7V would cause System.out.println(request.getParameter(ZAZBZ)); to print CZlYnXtAIBDC=D9W7V in Tomcat 3.2.3. But in tomcat 4.0.4 the printout is CZlYnXtAIBDC The results are the same when the URL is encoded because = remains the same. Looks like parameter value cannot contain = Please let me know if I am missing something. Sincerely, Vijay - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
