If I understand the history of this issue correctly, then we had a fix, but that got reverted, because it clashed with pre-existing code (IQHandlers in certain plugins).
I favor being spec-compliant by default. If we have plugins that choose not to (which arguably is a bug in those plugins or in the protocol that they implement), then Openfire could facilitate that by having an opt-out mechanism.
Guus der Kinderen November 16, 2023 at 8:59 AM
Behavior remains the same in 4.8.0-SNAPSHOT:
Daryl Herzmann November 13, 2017 at 2:39 PM
Anybody able to comment on the status of this issue?
RFC 6120:
Currently Openfire returns a non-error response, e.g. when sending: