test599 1.4 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586
  1. <testcase>
  2. <info>
  3. <keywords>
  4. HTTP
  5. HTTP POST
  6. chunked Transfer-Encoding
  7. </keywords>
  8. </info>
  9. #
  10. # Server-side
  11. <reply>
  12. <data>
  13. HTTP/1.1 302 OK
  14. Date: Thu, 09 Nov 2010 14:49:00 GMT
  15. Server: test-server/fake
  16. Location: 5990001
  17. Content-Length: 6
  18. Connection: close
  19. Content-Type: text/html
  20. -foo-
  21. </data>
  22. <data1>
  23. HTTP/1.1 200 OK
  24. Date: Thu, 09 Nov 2010 14:49:00 GMT
  25. Server: test-server/fake
  26. Transfer-Encoding: chunked
  27. Connection: close
  28. Content-Type: text/html
  29. 32
  30. this data is slightly larger than the first piece
  31. 0
  32. </data1>
  33. <datacheck>
  34. HTTP/1.1 302 OK
  35. Date: Thu, 09 Nov 2010 14:49:00 GMT
  36. Server: test-server/fake
  37. Location: 5990001
  38. Content-Length: 6
  39. Connection: close
  40. Content-Type: text/html
  41. HTTP/1.1 200 OK
  42. Date: Thu, 09 Nov 2010 14:49:00 GMT
  43. Server: test-server/fake
  44. Transfer-Encoding: chunked
  45. Connection: close
  46. Content-Type: text/html
  47. this data is slightly larger than the first piece
  48. </datacheck>
  49. </reply>
  50. # Client-side
  51. <client>
  52. <server>
  53. http
  54. </server>
  55. # tool is what to use instead of 'curl'
  56. <tool>
  57. lib599
  58. </tool>
  59. # Bug 3510057 pointed out that when following a location to a larger chunked
  60. # encoded page, the first size would still be used in the progress callback
  61. <name>
  62. HTTP GET with progress callback and redirects changing content sizes
  63. </name>
  64. <command>
  65. http://%HOSTIP:%HTTPPORT/599 log/ip599
  66. </command>
  67. </client>
  68. #
  69. # Verify data after the test has been "shot"
  70. <verify>
  71. <file name="log/ip599">
  72. CL: -1
  73. </file>
  74. </verify>
  75. </testcase>