2

I need to programmatically log into a backend server, which returns an auth token as a cookie, then use that cookie to make requests going forward. I'm working in Lift 2.4, and everything I read seems to recommend using http-dispatch, but that has been cumbersome to learn! :-/ I'm working in dispatch-classic because of my SBT version (0.1-SNAPSHOT) and scala version 2.9.1. So I'm currently loading the dispatch 0.8.6 libraries.

I found the following at https://groups.google.com/forum/#!msg/dispatch-scala/m7oWv2YAtjQ/imnkYoCDVUcJ

For retrieving cookies:

To read a cookie from a response, you have to call the Response#getCookies method. For example, you could do something like this:

val res = Http(url("http://www.google.com/ig/api").addQueryParameter("weather", "Bonn, Germany"))
val response = for { r <- res } yield (r.getCookies, r.getResponseBody)

for adding cookies to subsequent requests:

url("http://www.google.com/ig/api").addCookie(cookie)

But I can't get this to work. My preference is code that works with dispatch 0.8.6, but if you can make it work in another version and don't see what that version won't work with my SBT and scala/Lift versions, I'll try using your recommended library version.

Urist McDev
  • 498
  • 3
  • 14
Mike
  • 916
  • 12
  • 14

1 Answers1

2

To get a the cookie, you should be able to do something like this:

Http(url("http://www.google.com/ig/api") <<? List("weather" -> "Bonn, Germany") >:> ((h) => h.get("Set-Cookie")))

That will request the URL, append the weather param, and then pass the response headers to a handler function which looks for the Set-Cookie header and returns an Option with the value, or None if it was not present.

To set a cookie, you can do:

Http(url("http://www.google.com/ig/api") <<? List("weather" -> "Bonn, Germany") <:< Map("Set-Cookie" -> "something") >| )

This will add the headers in the Map following the <:< directive, which in the case above includes the cookie. The >| handler simply ignores the response, but you can use any handler you want.

This guide is a pretty good reference for the different functions and handlers available.

I checked this out with 0.8.8, as I don't have the earlier version, and everything seemed to work for me. I can't sure for sure, but I think it should be the same with 0.8.6.

jcern
  • 7,798
  • 4
  • 39
  • 47
  • Brilliant! I even understand a good chunk of that Periodic Table that stumped me the first 5 times reading it... For completeness, this request was for communicating between 2 servers, so I use "Set-Cookie" in one direction to emulate the backend server telling the calling server to "set a cookie" as if it were a browser, but on subsequent calls to the backend, I use "Cookie" to emulate the use of existing cookies... I think I could call it *any* custom header name at this point, but I stuck with standard conventions... – Mike Sep 10 '13 at 05:16