Setting up Repose: The REstful PrOxy Service Engine

Post to Twitter

From the Repose website: Repose is an open-source RESTful HTTP proxy service that scales to the cloud. Repose provides the solution to common API processing tasks such as rate limiting, client authentication, versioning, and logging so that web service developers can focus on the unique features of their services.

The Repose source code is available on GitHub. All files contained in Repose are licensed either under the Apache License v2.0 or the GNU General Public License v2.0.

If you were at the recent Openstack conference you may have heard of Repose already since the Repose client authentication component supports an OpenStack Identity Service authentication scheme.

Today I’ll walk through how to use a few of the Repose filters: Rate Limiting, HTTP Logging, Default Router, and IP Identity. Repose has several filters, so feel free to explore whats available. I’ll be setting up the standalone version of Repose but keep in mind you can also deploy it under an application server like Apache Tomcat.

[ad name=”Google Adsense”]

For more detailed information you can check out the Repose documentation located here.

I’ll be setting this up on OS X Lion using the JDK 1.7 from Oracle. I have a previous article on how to get Java JDK 1.7 setup on OS X Lion. I’ll place Repose in front of Atom Hopper (Atom Hopper is a an AtomPub server). You can get more information about Atom Hopper here.

First, we will setup Atom Hopper. Download Apache Tomcat 7 and extract it in your home directory. Grab a copy of the latest Atom Hopper WAR file and place it into the Apache-Tomcat/webapps folder. Rename the Atom Hopper WAR file to ROOT.war. If ROOT already exists you can delete it, or you can simply modify the path later on in this article. If you have Netbeans 7 with Maven feel free to build your own copy of Repose and Atom Hopper if you wish.

You will need to create three folders for Atom Hopper:

Note: Make sure those folders allow permission for user starting Atom Hopper to have read and write access.

Grab a copy of the following files and copy them to the /etc/atomhopper/ folder:

We will just leave those config files as the default settings which will use H2 as the database and a single feed as: namespace/feed For more information on using Atom Hopper see the wiki or my previous articles.

At this point you can start Apache Tomcat by going into the Tomcat bin folder and running:

$ ./

With Tomcat running Atom Hopper now we can test to ensure it’s working with the following URL: http://localhost:8080/namespace/feed/ You should just get some minimal default XML back since there is nothing in the database. Follow this article to learn how to put an ATOM entry into Atom Hopper.

Now we will focus on Repose.

Create the following folders and make sure the permissions are set that the user starting Repose has read and write access to those folders.
Configuration files: /etc/repose/
EAR file drop location: /usr/share/repose/filters/
Valve location (this is the standalone Repose location): /usr/share/lib/repose/
Log file location: /var/log/repose/
Deployment location (where the EAR is extracted): /var/repose/

In the configuration folder ( /etc/repose/ ) add all the following files at this location:

Add the IP identity config file ( /etc/repose/ ):

Add the rate limiting config file ( /etc/repose/ ):

Add the HTTP logging config file ( /etc/repose/ ):

In the EAR file drop folder ( /usr/share/repose/filters/ ) add the latest release from this location:

In the Valve location ( /usr/share/lib/repose/ ) copy in the latest Valve JAR release:

Since I have Tomcat with Atom Hopper running on port 8080 I’m going to set Repose to listen on port 8888. Keep in mind in a production environment you would most likely have Repose listening on port 80 and then forwarding to port 8080 to Tomcat.

I’ve modified the following config files in /etc/repose/


<?xml version="1.0" encoding="UTF-8"?>

<repose-container xmlns=''>
    <deployment-config http-port="8888" connection-timeout="30000" read-timeout="30000">
        <deployment-directory auto-clean="false">/var/repose</deployment-directory>
        <artifact-directory check-interval="60000">/usr/share/repose/filters</artifact-directory>
        <logging-configuration href=""/>



<?xml version="1.0" encoding="UTF-8"?>

<http-logging xmlns="">
	<!-- The id attribute is to help the user easily identify the log -->
	<!-- The format includes what will be logged.  The arguments with % are a subset of the apache mod_log_config
		 found at -->
	<http-log id="my-special-log" format="Response Code Modifiers=%200,201U\tModifier Negation=%!401a\tRemote IP=%a\tLocal IP=%A\tResponse Size(bytes)=%b\tRemote Host=%h\tRequest Method=%m\tServer Port=%p\tQuery String=%q\tTime Request Received=%t\tStatus=%s\tRemote User=%u\tURL Path Requested=%U\n">
			<!-- The actual log file -->
			<file location="/var/log/repose/repose.log"/>
	<http-log id="my-other-log" format="Remote IP=%a Local IP=%A">
			<file location="/var/log/repose/repose_other.log"/>


<?xml version="1.0" encoding="UTF-8"?>

<ip-identity  xmlns:xsi=''

    <white-list quality="1.0">


<?xml version="1.0" encoding="UTF-8"?>

<rate-limiting delegation="false" xmlns="">
        Defines an endpoint with a matching regex to bind GET requests for
        returning live rate limiting information.
    <request-endpoint uri-regex="/limits/" limits-format="OPENSTACK" />
        Defining a limit group.

        The following headers can be found in the class in the Power API
        Filterlet library, maven group id, artifact
        id filterlet.

        Groups are matched on the HTTP header: X-PP-Groups
        User information is matched on the HTTP header: X-PP-User
    <limit-group id="standard-ip-limits" groups="IP_Standard">
        <limit uri="/*" uri-regex="/(.*)" http-methods="GET" unit="SECOND" value="3" />

    <limit-group id="standard-ip-limits-superuser" groups="IP_Super">
        <limit uri="/*" uri-regex="/(.*)" http-methods="GET" unit="SECOND" value="5" />

Finally, edit the system-model.cfg.xml (this is where you enable each filter you want to use):

<?xml version="1.0" encoding="UTF-8"?>

<system-model xmlns="">
  <repose-cluster id="repose">
      <node id="node1" hostname="localhost" http-port="8888"/>
      <filter name="header-id-mapping" />
      <filter name="ip-identity" />
      <filter name="rate-limiting" />
      <filter name="http-logging" />
      <filter name="default-router"/>
      <endpoint id="openrepose" protocol="http" hostname="localhost" root-path="/" port="8080" default="true"/>

I won’t go through all the possibilities of how you can use HTTP Logging or Rate Limiting, etc. Refer to the docs for that information but suffice to say that Repose is extremely configurable.

Assuming everything is set correctly you can now run Repose:

$ java -jar valve-2.1.1.jar start -p 8888 -s 8188 -c /etc/repose/

The command above makes Repose listen on port 8888 (which is configured to proxy to Tomcat on port 8080). The port 8188 is the port Repose listens on for a shutdown command. This can done with a simple HTTP GET to this address: http://localhost:8188/ The final argument tells Repose to look in the /etc/repose/ folder for the configuration files.

Have a peek into the repose.log file once you’ve done an HTTP GET to Atom Hopper: http://localhost:8888/namespace/feed/

Response Code Modifiers=-	Modifier Negation=0:0:0:0:0:0:0:1%0	Remote IP=0:0:0:0:0:0:0:1%0	Local IP=0:0:0:0:0:0:0:1%0	Response Size(bytes)=2048	Remote Host=0:0:0:0:0:0:0:1%0	Request Method=GET	Server Port=8888	Query String=null	Time Request Received=04-06-2012-02:04:44.826	Status=304	Remote User=0:0:0:0:0:0:0:1%0;q=0.2	URL Path Requested=http://localhost:8080/namespace/feed

Response Code Modifiers=-	Modifier Negation=0:0:0:0:0:0:0:1%0	Remote IP=0:0:0:0:0:0:0:1%0	Local IP=0:0:0:0:0:0:0:1%0	Response Size(bytes)=2048	Remote Host=0:0:0:0:0:0:0:1%0	Request Method=GET	Server Port=8888	Query String=null	Time Request Received=04-06-2012-02:04:44.989	Status=404	Remote User=0:0:0:0:0:0:0:1%0;q=0.2	URL Path Requested=http://localhost:8080/favicon.ico

Play around with the rate limiting and rate limit yourself to see it in action.

Post to Twitter

This entry was posted in Apache Tomcat, Atom Hopper, Java, Open Source, Repose. Bookmark the permalink.

6 Responses to Setting up Repose: The REstful PrOxy Service Engine

  1. Shikha Jain says:

    We don’t find much information on Scalability and Auth/Auth extensibility in the Internet. Could you throw some more light on these features?
    And can Repose work with JBoss ?

  2. Chad Lung says:

    Repose should work with JBoss. I would try their mailing list for more information:


  3. Diego says:

    Thanks Chad.

    I’m trying to build Repose with maven. However, I get this error. Any ideas?

    Failed tests: shouldUnpackDirectoryStructure(com.rackspace.papi.commons.util.classloader.ear.EarUnpackerTest$WhenUnpackingEars): Should delete deployment directory

    Tests run: 16, Failures: 1, Errors: 0, Skipped: 2

  4. Chad Lung says:


    Check with the Repose mailing lists for any issues on how to get the build working:


  5. Diego says:

    Thanks Chad. Maven build wasn’t compatible with Window. Ran the build on a Mac and it ran fine. Got it from the IRC channel.

    Also found similar tutorial as your in case anybody want to expand on it.

  6. Chad Lung says:


    Yeah both Atom Hopper and Repose need to be built on Linux or OS X.

    I wrote that other article you mentioned BTW.


Comments are closed.