Here's some personalized content. Personalized web page 5. Two methods for support are described here, with their associated advantages and disadvantages explained. The general approach is to allow applet invocations on OPS profile request pages to interact with an OPS client side library, fulfill the request, and redirect the browser to the target page with the profile object included. That failure content in turn invokes a Java applet, passing parameters including the GetProfile header value.
User agent ignores header, but invokes applet.
Applet evaluates profile request by interacting with trusted code, possibly asks for user permission. If the profile data is adequate, server returns the personalized content. If incorrect, server sends request and applet invocation in response and the process repeats. Most often, this functionality is invoked via the use of custom MIME types. If the profile data is adequate, server returns the personalized content.