You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
for (int i=1; i<chunkSequenceNumbers.size(); i++)
if (chunkSequenceNumbers.get(i) != chunkSequenceNumbers.get(i-1)-1) {
String msg = "Sequence numbers of chunks are not consecutive";
log.info(msg);
setError(new ServiceResultException(StatusCodes.Bad_DecodingError, msg));
return;
}
Look closely at "chunkSequenceNumbers.get(i) != chunkSequenceNumbers.get(i-1)-1".
This means if a message is broken into chunks and sequence numbers are 3, 4, 5.
Then it won't pass validation unless sequence numbers are passed as "5,4,3".
The text was updated successfully, but these errors were encountered:
Could you please describe the scenario which causes this, e.g. does this happen together with a specific client/server? Can it be reproduced easily? The reason I ask is because the stack has participated directly and indirectly in the IOP Workshops for many years, which should already have minimized these kinds of problems by noticing them early.
P.S. For future issues, please mention the class in question where the code is. (this code is in SecureInputMessageBuilder class).
for (int i=1; i<chunkSequenceNumbers.size(); i++)
if (chunkSequenceNumbers.get(i) != chunkSequenceNumbers.get(i-1)-1) {
String msg = "Sequence numbers of chunks are not consecutive";
log.info(msg);
setError(new ServiceResultException(StatusCodes.Bad_DecodingError, msg));
return;
}
Look closely at "chunkSequenceNumbers.get(i) != chunkSequenceNumbers.get(i-1)-1".
This means if a message is broken into chunks and sequence numbers are 3, 4, 5.
Then it won't pass validation unless sequence numbers are passed as "5,4,3".
The text was updated successfully, but these errors were encountered: