I'm using Windows.Web.Http.HttpClient in a universal app to access some web API, and I noticed that on some of the responses' headers, there are Set-Cookie items which are values that needs to be sent on subsequent API calls. However, I'm not seeing those
values set on subsequent API calls. I'm sure I missed something but I can't figure out what I missed. Here's the code I used:
using Windows.Web.Http.HttpClient;
HttpBaseProtocolFilter _httpFilter = new HttpBaseProtocolFilter();
HttpClient _httpClient = new HttpClient(_httpFilter); //Is this necessary to include filter?
string _urlBase = "https://my.hostname.com/api/"
Uri uri = new Uri(_urlBase+"login");
HttpRequestMessage req_msg1 = new HttpRequestMessage(HttpMethod.Post, uri);
req_msg1.Content = new HttpStringContent(somestring);
req_msg1.Content.Headers.ContentType = new Windows.Web.Http.Headers.HttpMediaTypeHeaderValue("text/xml; charset=UTF-8");
req_msg1.Headers.Host = new Windows.Networking.HostName("my.hostname.com");
HttpResponseMessage rsp_msg1 = await _httpClient.SendRequestAsync(req_msg1);
//rsp_msg1 will contain Set-Cookie header like this:
//Set-Cookie: JSESSIONID=7EF8967C290413A4354AFD1A6DFF9FC8; Path=/api; HttpOnly
//Set-Cookie: KEY1=VALUE1; path=/
Uri uri2 = new Uri(_urlBase+"check");
HttpRequestMessage req_msg2 = new HttpRequestMessage(HttpMethod.Post, uri2);
req_msg2.Content = new HttpStringContent(someotherstring);
req_msg2.Content.Headers.ContentType = new Windows.Web.Http.Headers.HttpMediaTypeHeaderValue("text/xml; charset=UTF-8");
req_msg2.Headers.Host = new Windows.Networking.HostName("my.hostname.com");
HttpResponseMessage rsp_msg2 = await _httpClient.SendRequestAsync(req_msg2);
What I'd like to see is that req_msg2 should contain the cookies with values from rsp_msg1. What should I do/should I not do?
