-Bad XML data can still come down, UTF-8 doesn't protect everything
git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@6602 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd
This commit is contained in:
parent
005d5996ab
commit
afe254b5ce
@ -1266,8 +1266,8 @@ sub convey_response {
|
||||
}
|
||||
$resp = XMLout($resp,KeyAttr=>[], NoAttr=>1,RootName=>'xcatresponse');
|
||||
#sanitize the response, to avoid being killed by non-printable bytes
|
||||
#$resp =~ tr/\011-\177/?/c;
|
||||
#seeing if using utf-8 offloads potential issues to client terminal
|
||||
$resp =~ tr/\011-\177/?/c;
|
||||
#seeing if using utf-8 offloads potential issues to client terminal, it didn't
|
||||
print $parent_fd $resp;
|
||||
yield; #parent must get timeslice anyway before an ack could possibly return
|
||||
my $parsel = new IO::Select;
|
||||
|
Loading…
Reference in New Issue
Block a user