Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.2.10
-
None
Description
This appears to be caused by inappropriate use of the URI's path member at the point where the GET is performed.
I have already tested a fix that works against 1.2.10 (released) code.
Also, looking at the trunk code, it appears that this bug remains, although the code affected in 1.2.10 has since been rewritten to use Net::HTTP (i.e., the rewrite still uses uri.path when uri.request_uri seems to be more correct).
I have not yet created a unit test to fail.
I'm not clear in my mind about the 'priority' on this, but I'm leaving it at 'Major' for now, because it breaks my organization's builds. I don't particularly care if the project management team sees fit to move the priority down on this.
I expect to submit one or more patches Real Soon Now (TM).