This makes sense from an internal point of view, but from a user's perspective it's kind of weird: You call removeRequestHeader and it doesn't get removed. I was wondering if we should modify HttpMethodBase so that it adds the default User-Agent header in the constructor and in recycle() instead. That way, removeRequestHeader would work.
If folks think this is a good idea, I'll submit a patch.
My only concern is that a method should contain a User-Agent header, according to the RFC. If people don't see this as such a big deal then I say go for it.
Mike
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
