Local proxy unable to correctly detect requests to itself

[GoogleCodeExporter]

Steps to reproduce the issue (watch out!):
1. Run ZAP and configure the local proxy to "127.0.0.1:8080";
2. Access ZAP with "127.0.0.1" (example: http://127.0.0.1:8080/), it works as 
expected (either the connection is closed in version 2.0.0 or the ZAP "Welcome" 
page is shown in trunk);
3. Access ZAP with "localhost" (example: http://localhost:8080/) and note that 
takes a little longer to receive a response;
6. Check the number of threads created by ZAP; Note that the number of threads 
is/was increasing at a fast pace. As the local proxy is unable to detect that 
the request is to itself it will keep requesting (recursively) to itself until 
it's no longer enable to create more threads (if it's fast creating threads) or 
until timeouts occur.

Remarks:
In just a couple of seconds, since the first "recursive" request, ZAP created 
4.401 threads and had a live peak of 3.204 threads (in the end all requests 
timed out and the "loop" was broken).

ZAP Version:
Version 2.0.0 (and trunk r3043).

Original issue reported on code.google.com by THC...@gmail.com on 12 Apr 2013 at 2:15

[GoogleCodeExporter]

r3059

Original comment by THC...@gmail.com on 14 Apr 2013 at 6:38

• Changed state: Committed

[GoogleCodeExporter]

Original comment by psii...@gmail.com on 15 Apr 2013 at 8:46

• Added labels: Build-20130415

[GoogleCodeExporter]

Fixed in 2.1.0

Original comment by psii...@gmail.com on 18 Apr 2013 at 9:49

• Changed state: Fixed