EWS: Fix 3471671, workaround for Exchange invalid chars
git-svn-id: http://svn.code.sf.net/p/davmail/code/trunk@1877 3d1905a2-6b24-0410-a738-b14d5a86fcbd
This commit is contained in:
parent
e55afcbec4
commit
cbeef8c00d
|
@ -2383,11 +2383,11 @@ public abstract class StreamScanner
|
||||||
if (value == 0) {
|
if (value == 0) {
|
||||||
throwParseError("Invalid character reference: null character not allowed in XML content.");
|
throwParseError("Invalid character reference: null character not allowed in XML content.");
|
||||||
}
|
}
|
||||||
// XML 1.1 allows most other chars; 1.0 does not:
|
// XML 1.1 allows most other chars; 1.0 does not: However Exchange sends such chars with XML 1.0
|
||||||
if (!mXml11 &&
|
//if (!mXml11 &&
|
||||||
(value != 0x9 && value != 0xA && value != 0xD)) {
|
// (value != 0x9 && value != 0xA && value != 0xD)) {
|
||||||
reportIllegalChar(value);
|
// reportIllegalChar(value);
|
||||||
}
|
//}
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue