=Comment: #0================================================= mirproxy <mirproxy.com> - 2008-03-25 13:53 EDT ---Problem Description--- Further testing of character processing ... Attempt to inject a 0x96 here ==>`<== End of test comments! Contact Information = Me ---uname output--- n/a Machine Type = n/a ---Debugger--- A debugger is not configured ---All Component Data---
grr ... wrong character ... try again! Attempt to inject a 0x96 here ==>û<== End of second test comment!
Add some debug and resend.
Attempt to inject another 0x96 here ==>û<== End of third test comment!
Hmm ... I'm stumped at the moment. During processing the character was transmitted as %BB: [2008.03.25 13:12:37.745 (QueueManager-6.modify.0.helper) bugzilla.custom.api.RHBugzillaBug-doProcessBug] PostMethod request = id=438876&knob=none&form_name=process_bug&longdesclength=1&bug_file_loc=&reporter_accessible=1&cclist_accessible=1&comment=Attempt+to+inject+another+0x96+here+%3D%3D%3E%C3%BB%3C%3D%3D%0AEnd+of+third+test+comment%21&target_milestone=---&product=Bugzilla&component=Test&reporter_accessible=1&qa_contact=&resolution=&serverurl=https%3A%2F%2Fbugzilla.redhat.com%2F&assigned_to=bugzilla-maint%40redhat.com&bug_severity=medium&public_release=&version=2.8&cclist_accessible=1&creation_ts=2008-03-25+13%3A55+EST&short_desc=Test+bug%3A+more+character+processing&reporter=mirproxy%40linux.vnet.ibm.com&rep_platform=other&op_sys=All&priority=low&reference=&defferedresolution=&fixedresolution=&rejectresolution=
More precisely, the character was transmitted as two bytes: %C3%BB%
Red Hat Bugzilla is now using version 3.2 of the Bugzilla codebase and therefore this bug will need to be re-verified against the new release. With the updated code this bug may no longer be relevant or may have been fixed in the new code. Updating bug version to 3.2.