[Standards] XEP-0198 stream resumption with too high 'h' parameter

Florian Schmaus flo at geekplace.eu
Tue Feb 14 14:12:45 UTC 2017

On 14.02.2017 12:17, Michal Piotrowski wrote:
> Hello,
> I'm currently investigating following situation. The server sent to the
> client 10 stanzas and clients sends accept <a h='11'/> which is not
> valid (too high).
> In XEP-0198 I didn't find any information what should happen if clients
> sends too high 'h' parameter. 
> What should be the server response in this case? The safest is probably
> to close the stream with error indicating a policy violation.
> Also what should happen if a client resumes a stream with such too high
> 'h' parameter?

In both cases close the connection with a stream-error including a
meaningful error condition and textual message (something like: "Client
send 'h' value of 123 is higher our maximum 'h' of 120").

- Florian

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 610 bytes
Desc: OpenPGP digital signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20170214/e8bdb887/attachment.sig>

More information about the Standards mailing list