2
0

test3018 1.1 KB

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