Added RepeatableInputStreamEntity.
Added unit test - not working
Fixed RepeatableInputStreamTest.
Allow whitelist to be cleared.

Implemented as both ProxyServer and REST DELETE call on /:port/whitelist
Allow blacklist to be cleared.

Implemented on both ProxyServer and REST DELETE call on /:port/blacklist
Document whitelist and blacklist clearing
Simple support for clearing all rewrite rules

Allows all current rewrite rules to be cleared at once. 
Exposes functionality as DELETE REST call to /:port/rewrite.
Document REST API for removing all rewrite rules
Create empty blacklist before first use

Fixes small chance of a race condition when several threads try and get 
/ set blacklist entries. Using a CopyOnWriteArrayList allows for 
concurrent readers and writers, but it needs to be initialised before 
first use to avoid race conditions the first time around.

Also makes it easier to clear the list in a concurrency-friendly way.
Simple test for rewrite rule clearing
Cleanup blacklist entries on shutdown

Just trying to copy what's happening with rewriteRules, to ensure we
do as much tidying as possible.
Guard against concurrent modification of whitelistEntry

Modifying blacklistEntry is thread-safe as it uses a thread-safe data 
structure (CopyOnWriteArray). whitelistEntry is not, as while it uses
a concurrent data structure to track the list of patterns, several
threads / HTTP calls may attempt to set the whitelist or clear the
whitelist concurrently.

Protecting these calls by synchronizing on the BrowserMobHttpClient 
instance should protect againt concurrent modification of the list, and
associated race conditions.
Unit test for black/white list clearing
Use spaces, not tabs. D'oh!
fix for slf4j compatibility issue
added test for reading POST parameters in a RequestInterceptor. It currently fails because when the POST parameter is read and printed out, it is removed from the request
Added setter for localhost InetAddress, to allow binding of proxy to a particular network interface.
Added check for valid InetAddress.
Replace User Agent Parser libs with [UADetector libs](http://uadetector.sourceforge.net/).

UADetector relies on the same external resources, but can rely on cached User Agent Strings in the lib, if `user-agent-strings.info` is not available.

Also, easy to keep cached datastore up-to-date by updating POM to latest/greatest UADetector in Maven Central.

A regression though, didn't maintain support `uaCache` option, doesn't seem necessary anymore sind UADetector should handle keeping it up-to-date.
confirms issue #27 is not a problem