Feature #4902
open
Better logging when Interest & Data don't match
0%
Description
I was trying to do a simple test, using the ndnpeek test application. I could see that the interest was reaching the producer and making its way back to NFD, but NFD was rejecting it as "unsolicited data".
It took me longer than it should have to realize that I'd neglected to include the -P flag. But when I look at the NFD log, it could definitely be a bit more informative. It shows that it looks up the name provided in the data and fails, then matches the name provided in the interest. At which point it says it's an unsolicited data packet.
I assume what is happening under the covers is that when it matches the prefix, it is looking for the CanBePrefix flag, not finding it, and declaring it to be unsolicited. A DEBUG or TRACE-level message to that effect would, I think, help what must be a somewhat common occurrence.
As Junxiao pointed out, this is a bug in the producer for responding with a prefix when the interest didn't allow it. But it's NFD that has the info that this mismatch has occurred -- it looks up the prefix, finds the pending interest, and decides that the two can't be paired. At that point it would be really easy to log a warning to that effect, or at least a debug/trace level message.
Updated by 
Updated by 
Updated by