Replies: 2 comments 2 replies
-
|
Hi @aranw Indeed, Sorry for the obvious suggestion but, in this case, couldn't you set the header on the first request, and not set it on the following requests (by not using # ─── Get S3 presigned upload URL ──────────────────────────────────────────────
PUT {{base_url}}/upload
Authorization: XXX
[Options]
location: false
HTTP 307
[Captures]
upload_url: header "Location"
# ─── Upload file to S3 ────────────────────────────────────────────────────────
PUT {{upload_url}}
Content-Type: image/png
[Options]
location: false
file,testdata/logo.png;
HTTP 200This supports also variables that you can inject: # ─── Get S3 presigned upload URL ──────────────────────────────────────────────
PUT {{base_url}}/upload
Authorization: {{token}}
[Options]
location: false
HTTP 307
[Captures]
upload_url: header "Location" |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
If i understand your use case, you want to run for instance : $ hurl --header "x-foo:FOO" --header "x-bar:BAR" test.hurlAnd in the Hurl file: # This request has `x-foo` header and `x-bar` header
GET https://example.com
HTTP 200
# This request has only `x-foo` header
# Syntax TBD
GET https://example.com
[Options]
no-header: x-bar
HTTP 200is this correct? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have this hurl file that will make a request to an endpoint which will return a presigned url
I then use that presigned url to upload a file but the issue I'm having is I set the authorization header via the
--headerflag and I'd like to exclude that header from the request that is made to the presigned urlIs there a way to make the second request not include the
--header authorization?Beta Was this translation helpful? Give feedback.
All reactions