You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to "capture" entire responses as files within chained requests. I would capture the image URLs and follow the first request with 3 more to get the images
GET /resource
HTTP/* 200
[Captures]
id: jsonpath "$.id"
image-small: jsonpath "$.images.small"
image-medium: jsonpath "$.images.medium"
image-large: jsonpath "$.images.large"
GET {{image-small}}
HTTP/* 200
[Captures]
save-as: {{id}}/small.jpg
GET {{image-medium}}
HTTP/* 200
[Captures]
save-as: {{id}}/medium.jpg
GET {{image-large}}
HTTP/* 200
[Captures]
save-as: {{id}}/large.jpg
```</div>
The text was updated successfully, but these errors were encountered:
GET https://foo.com
[Options]
output: /tmp/out.bin
HTTP 200
GET https://bar.com
If you know how to build a Rust program, I would be graceful to get feedback on the feature. In any case, the option will be available in the next Hurl release.
Discussed in #1323
Originally posted by tpluscode March 2, 2023
I have a resource like this:
It would be nice to "capture" entire responses as files within chained requests. I would capture the image URLs and follow the first request with 3 more to get the images
The text was updated successfully, but these errors were encountered: