Black-Listing with Charles Proxy

[Matyjas]

Hi,

First of all, thanks for a great communications library!

My client is using Charles Proxy (http://www.charlesproxy.com/) as
part of their testing process and has flagged a potential issue. I
have reproduced this issue using the current iPhone Sample project
from github.

Here are the steps to reproduce:

- Run Charles Proxy (30 day free trial)
- Click to Tools -> 'Black List' then add http://allseeing-i.com to
the list of blocked sites
- Make sure Charles Proxy is recording
- Run Sample Project in Simulator (the iPad version worked for me)
- Click Go! in the Synchronous Request view or Queue view of the
Sample project
- Inspect Charles Proxy, where it looks like there is an infinite loop
on the blocked request

I am not sure if this is a 'real' issue because when I go through the
same sequence with Instruments there seem to be no adverse effects in
the client code (barring a few leaks in the Sample project). The
client code nicely returns a 'timed out' error and things seem fine.

Any info would be appreciated!

Thanks!

Maciej

[Ben Copsey]

Hi Maciej

> My client is using Charles Proxy (http://www.charlesproxy.com/) as
> part of their testing process and has flagged a potential issue. I
> have reproduced this issue using the current iPhone Sample project
> from github.
>
> Here are the steps to reproduce:
>
> - Run Charles Proxy (30 day free trial)

I can recommend spending the money - Charles is the nicest http debugging tool I've tried. :)

> - Click to Tools -> 'Black List' then add http://allseeing-i.com to
> the list of blocked sites
> - Make sure Charles Proxy is recording
> - Run Sample Project in Simulator (the iPad version worked for me)
> - Click Go! in the Synchronous Request view or Queue view of the
> Sample project
> - Inspect Charles Proxy, where it looks like there is an infinite loop
> on the blocked request
>
> I am not sure if this is a 'real' issue because when I go through the
> same sequence with Instruments there seem to be no adverse effects in
> the client code (barring a few leaks in the Sample project). The
> client code nicely returns a 'timed out' error and things seem fine.

I don't think this is anything to worry about. As far as I can see the request simply starts and times out. From a quick debug run it looks like the request doesn't receive any response, and from the logs I can see that it doesn't reach the server (as you would expect).

Presumably the fact that the request is listed multiple times is a bug in Charles - it does show that the address is blacklisted.

Best

Ben