Creating an Access Manager Reverse Proxy for LexisNexis Academic


Creating an Access Manager Reverse Proxy for LexisNexis Academic


The problem with the LexisNexis functioning properly “out of the box” is that the website uses an AJAX script browser side to generate it's URLs. This creates a problem because Access Manager's rewriter does not rewrite URLs from the browser to the Web server, but from the web server to the browser.

See Figure 1 which is a HTTPREPLAY of an STRACE log file.

Click to view.

Figure 1

The first thing to do is setup a new reverse proxy with the following information.

Click to view.

Figure 2

Click to view.

Figure 3

The complete list of Additional DNS Names are as follows:

Then create a new Character HTML Rewriter Profile List and move it above any existing rewriter policies you have in place.

Click to view.

Figure 4

The LexisNexis service sends back mis-formatted text with escape characters so we need to replace them with your published DNS name. As you can see in Figure 4, format the string to replace http:\/\/ with your published DNS name (

Add a protected resource for /hottopics/lnacademic and /*.

Click to view.

Figure 5

We then need to create another reverse proxy with the Published DNS Name as:

We need to add this secondary proxy because of the way that LexisNexis has browser side URL creation but has written in this work around for Reverse Proxy servers like Access Manager.

Click to view.

Figure 6

Setup the webservers tab the same as the first proxy (Figure 2). You do not need to add the Additional DNS Names to this proxy.

Setup the second proxies Protected Resource as /*.

Commit these changes and your proxy should be functional.


How To-Best Practice
Comment List