xref: /curl/tests/data/test3017 (revision f81f351b)
1<testcase>
2<info>
3<keywords>
4MQTT
5MQTT SUBSCRIBE
6</keywords>
7</info>
8
9#
10# Server-side
11<reply>
12<data nocheck="yes">
13hello
14</data>
15<datacheck hex="yes">
1600 04 33 30 31 37   68 65 6c 6c 6f 5b 4c 46 5d 0a
17</datacheck>
18<servercmd>
19excessive-remaining TRUE
20</servercmd>
21</reply>
22
23#
24# Client-side
25<client>
26<features>
27mqtt
28</features>
29<server>
30mqtt
31</server>
32<name>
33MQTT SUBSCRIBE with pathological PUBLISH length
34</name>
35<command option="binary-trace">
36mqtt://%HOSTIP:%MQTTPORT/%TESTNUMBER -m 3
37</command>
38</client>
39
40#
41# Verify data after the test has been "shot"
42<verify>
43# These are hexadecimal protocol dumps from the client
44#
45# Strip out the random part of the client id from the CONNECT message
46# before comparison
47<strippart>
48s/^(.* 00044d5154540402003c000c6375726c).*/$1/
49</strippart>
50# on Windows the disconnect is never seen - no idea why
51<strip>
52^server DISCONNECT 0 e000
53</strip>
54<protocol>
55client CONNECT 18 00044d5154540402003c000c6375726c
56server CONNACK 2 20020000
57client SUBSCRIBE 9 000100043330313700
58server SUBACK 3 9003000100
59server PUBLISH c 30ffffff8000043330313768656c6c6f0a
60</protocol>
61
62# 8 is CURLE_WEIRD_SERVER_REPLY
63<errorcode>
648
65</errorcode>
66</verify>
67</testcase>
68