Supress the usual mime warnings from mime4j

Supress "Body part ended prematurely" and "Unexpected end of headers detected".
I believe these happens because we feed partial messages to the parser.

We've kept these logs only "just in case", but I don't think it's ever been
usueful...

Change-Id: I29e5e48abf71612eed656ce6569246caf8a320bc
This commit is contained in:
Makoto Onuki 2011-06-26 14:02:52 -07:00
parent f9a9f52897
commit 178e2930e7
1 changed files with 11 additions and 11 deletions

View File

@ -157,12 +157,12 @@ public class MimeStreamParser {
parseBodyPart(tempIs); parseBodyPart(tempIs);
tempIs.consume(); tempIs.consume();
if (tempIs.parentEOF()) { if (tempIs.parentEOF()) {
if (log.isWarnEnabled()) { // if (log.isWarnEnabled()) {
log.warn("Line " + rootStream.getLineNumber() // log.warn("Line " + rootStream.getLineNumber()
+ ": Body part ended prematurely. " // + ": Body part ended prematurely. "
+ "Higher level boundary detected or " // + "Higher level boundary detected or "
+ "EOF reached."); // + "EOF reached.");
} // }
break; break;
} }
} }
@ -247,11 +247,11 @@ public class MimeStreamParser {
prev = curr == '\r' ? prev : curr; prev = curr == '\r' ? prev : curr;
} }
if (curr == -1 && log.isWarnEnabled()) { // if (curr == -1 && log.isWarnEnabled()) {
log.warn("Line " + rootStream.getLineNumber() // log.warn("Line " + rootStream.getLineNumber()
+ ": Unexpected end of headers detected. " // + ": Unexpected end of headers detected. "
+ "Boundary detected in header or EOF reached."); // + "Boundary detected in header or EOF reached.");
} // }
int start = 0; int start = 0;
int pos = 0; int pos = 0;