Apologies in advance, this report is going to be pretty awful, because I'm encountering this issue when accessing a private URL and I don't have a good test bed set up at the moment.
I'm posting to a URL, that when accessed using cURL, python via requests, and a web browser responds correctly with two set-cookie headers. Surf is only returning the second of the two headers, despite the documentation claiming that it should contain all of them.
This only returns the second header:
let response = surf::post(URL)
.body(surf::Body::from_form(&form)?)
.send()
.await?;
let headers = response
.header(surf::http::headers::SET_COOKIE).unwrap();
dbg!(headers.get(0)); // Some("cookie2")
dbg!(headers.get(1)); // None
But when inspecting an identical request from cURL:
Apologies again for the lack of details, I'll try to put together/find some test endpoint that returns two set-cookie headers to provide as reproduction soon.
Apologies in advance, this report is going to be pretty awful, because I'm encountering this issue when accessing a private URL and I don't have a good test bed set up at the moment.
I'm posting to a URL, that when accessed using cURL, python via
requests
, and a web browser responds correctly with twoset-cookie
headers. Surf is only returning the second of the two headers, despite the documentation claiming that it should contain all of them.This only returns the second header:
But when inspecting an identical request from cURL:
Or when using
requests
in python it correctly returns both:Apologies again for the lack of details, I'll try to put together/find some test endpoint that returns two
set-cookie
headers to provide as reproduction soon.