test599 1.4 KB

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