Comment # 15
on bug 8070
from Shoichi Sakane
(In reply to comment #14)
> To make sure I've understood this correctly: in previous versions of the
> spec, If-None-Match options carried a payload, now they don't, so that code
> can be removed.
Actually, If-None_Match option doesn't have a payload from its early stage.
The code tried to decode the option as same way as "If-Match" option. That was
a bug.
> But there is no way to filter on packets containing If-None-Match options
> because there are no fields for them now. Shouldn't the option type itself
> be a field that can be filtered on?
It might be. But, I don't think it is required currently.
Shoichi
You are receiving this mail because:
- You are watching all bug changes.