Show description

9 HTTP Redirects HTTP redirects are an important part of many web applications. In Lift there are two main ways of sending a redirect to the client: 1. redirectTo. When you do this, Lift throws an exception and catches it later on. This means that any code following the redirect is skipped. redirectTo so that your snippet instance is used when the redirect is processed. redirectTo within a try/catch block, you’ll need to make sure that you aren’t catching the redirect exception (Scala uses unchecked exceptions), or test for the redirect’s exception and rethrow it.

This is really just a fragment and is not intended to be used alone, since it’s not a full XHTML document and it doesn’t surround itself with a master template. It does, however, provide binding sites that we can fill in. 7: The Embedded Expense Table 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

20 19 CHAPTER 2.

Cookies are easy to fake, so you need to ensure that you validate any sensitive cookie data Using Cookies in Lift is very easy. In a stateful context, everything you need is provided by a few methods on the S object: addCookie Adds a cookie to be sent in the response deleteCookie Deletes a cookie (technically, this adds a cookie with a maximum age of zero so that the browser removes it). You can either delete a cookie by name, or with a Cookie object findCookie Looks for a cookie with a given name and returns a Box[Cookie].

Download PDF sample