Bug 1320004

Summary: 500 error if search input is special characters in the editusers.cgi
Product: [Community] Bugzilla Reporter: Rony Gong 🔥 <qgong>
Component: AdministrationAssignee: PnT DevOps Devs <hss-ied-bugs>
Status: CLOSED DUPLICATE QA Contact: tools-bugs <tools-bugs>
Severity: low Docs Contact:
Priority: medium    
Version: 5.0CC: huiwang, jmcdonal, mtahir, qgong
Target Milestone: 5.0   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-20 06:36:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
bz.log none

Description Rony Gong 🔥 2016-03-22 06:03:22 UTC 
Description of problem:
500 error when search kinds of character in the editusers.cgi

Version-Release number of selected component (if applicable):
5.0.2.rh2

How reproducible:
100%


Steps to Reproduce:
1.Go to https://$Server/editusers.cgi  by admin
2.Input "@#￥%……&*（）-=" in the matching input, click search button
3.

Actual results:
Internal Server Error             
The server encountered an internal error and was unable to complete your request.
Error 500

Expected results:
No 500 error and without any user return.

Additional info
Comment 1 Jeff Fearn 🐞 2016-04-20 00:09:44 UTC 
Please attach the error from the error log.
Comment 2 Rony Gong 🔥 2016-04-20 01:23:57 UTC 
(In reply to Jeff Fearn from comment #1)
> Please attach the error from the error log.

There is no error log present in error_log, and only caught some log from bz.log, check the attachment.
Comment 3 Rony Gong 🔥 2016-04-20 01:24:13 UTC 
Created attachment 1148828 [details]
bz.log
Comment 4 Jeff Fearn 🐞 2016-04-20 06:36:29 UTC 
@, #, etc work for me on the official devel server but UTF8 chars cause the 500. All of them work fine on my devel server.

*** This bug has been marked as a duplicate of bug 1318879 ***