{"author":"Jay Satiro","author_email":"raysatiro@yahoo.com","author_time":1737793030,"commit_time":1737876561,"committer":"Jay Satiro","committer_email":"raysatiro@yahoo.com","hash":"1a36923d73bf9c7ac234bdf9aaa1c1eca9fdbc5e","message":"tests: change the behavior of swsbounce\n\n- Change the swsbounce keyword to override the part number on a\n  subsequent request to the previous part number + 1.\n\nNote the previous part number in this case is the part number that\nwas returned as a response to the previous request and contained\nthe swsbounce keyword.\n\nPrior to this change swsbounce incremented the part number of the\nsubsequent request instead of overriding it, and did so in a more\nlimited fashion that prevented chaining swsbounce in multiple responses.\n\nFor example, if the test makes a request that causes the sws server to\nreturn `<data>` as a response and that response contains `swsbounce`\nthen for the next response the sws server returns `<data1>`. If\n`<data1>` also contains `swsbounce` then for the next response the sws\nserver now returns `<data2>` instead of the requested part.\n\nFixes https://github.com/curl/curl/discussions/16074\nCloses https://github.com/curl/curl/pull/16085\n","parents":["516cb98733ac6703bc5c5db3b37aff9bbfbd3ac1"],"tree_hash":"3783d5dea4ccd21fede23ffefe170dc1802d555f"}