I like to have a failsafe setup where net_connects are disallowed by default.
I've implemented a method for specifying some URIs which are whitelisted.

Please let me know if I need more test coverage, or if the implementation could be more obvious.

The branch "passthrough" is on my fork.
halorgium@15f5eb2

The soap4r gem currently uses httpclient gem which is not currently disabled when used with fakeweb (allow_net_connect = false).

It looks as though some work has been done at http://github.com/dkubb/fakeweb/commit/430bdc3cbed18d38f8a2391053c26e9e2262d671 although it is now a bit out of date.

Right now, the query params of the incoming request are sorted by key before we try to match against all the registered Regexps and URI objects. This works fine for URIs, because we can sort those query params too, so the user doesn't even know.

For Regexps, though, it seems impossible to figure out what part of the Regexp represents the query params and sort it; so the user has to be aware that their Regexp must be written to match against sorted params. That can be kind of hard sometimes. For example, a registration might look something like:

/example\.com\?[z\d]{2}=1&(opt1=a|opt2=b)$/

To match this URI:

http://example.com?9z=1&opt2=b

But also this URI:

http://example.com?zz=1&opt1=a

So you can see that if we sorted the second URI's params by key, it wouldn't match the Regexp. Instead, the user would have to register a Regexp that matches either order (or do two register_uri calls), which is pretty ugly.

We tried getting around this by calculating all the possible orders of the params and matching them, but that's O(n!) and therefore intractable for even pretty reasonable query params counts.

So the idea is that we could add a new API entirely, and get the query params out of the Regexp. Maybe an additional argument to register_uri with a hash of params that must in the request?

(Forked from issue #5.)

According to the stats on rubyforge and gemcutter, it looks like a few users are still installing the old FakeWeb versions of the gem.

We could probably ask to have them removed outright, since the pre-1.2.0 gem versions are still available as "fakeweb" gems.

I think a nicer solution would be to do a final release in the 1.1.x series that uses RubyGems's post-install hook to print out a note about the FakeWeb -> fakeweb change. Maybe add a warning when that version is required, too. It might be annoying, but the exact same versions of the gems exist under the fakeweb name, so switching should be pretty easy for anyone still using the old gems.

Add support for Curb.

There are a lot of situations when we need to stub FTP calls. It would be awesome to implement such functionality for that gem. I could help you with that.