Community
Participate
Working Groups
Recording fails on Windows Vista. IE7 fails as if there is no network. Firefox fails with the complaint: "The proxy server is refusing connections".
Changed severity to blocker (on Vista platform)since without recording capability, URL Test in TPTP and any consuming product that uses the HTTP recorder to generate tests is pretty much non-functional. It is recognized of course that Windows Vista is not a supported platform for 4.2.1, but it is a target platform being seriously considered for tolerance by Eclipse 3.2.2 (which TPTP 4.2.2 would align with), and Vista support in Eclipse and the other Eclipse projects such as TPTP is needed for consuming products to support Windows Vista. This defect should be targeted to the first TPTP release for which Vista tolerance is targeted.
Since 4.2.2 does not support Vista, decreasing to a critical severity. Moving forward, TPTP will be looking at the cost to adding Vista as a supported platform for 4.2.2/4.4. Mark: Please provide a rough sizing for this defect?
We found the source of the problem. The recorder calls regedit to modify the registry settings, and tells the browser to send all its HTTP traffic to "localhost" on port 1080 (where the Recorder is listening. The hosts file (C:\windows\system32\drivers\etc\hosts) on Vista has two entries in it for localhost, one specifying the IPv4 address and the other specifying the IPv6 address (see below). No matter which order they are found in the hosts file, when you ping localhost, it always uses the IPv6 address. ::1 localhost 127.0.0.1 localhost When I modified the hosts file and commented out the IPv6 address for localhost, the recorder worked fine. Another option could be employed in which the user would not have to edit the hosts file. In this case, the user could set the 'application to record' to 'NONE', and manually configure Internet Explorer to point to 127.0.0.1 (rather than 'localhost') and port 1080. I have tested this and it works as well. All the testing we have done so for on Vista was done with the User Access Controls (UAC) turned off. We must perform the same testing with the UAC turned on and see if this causes any additional problems.
(In reply to comment #3) Great work Mark, Joe and Duwayne! What exactly is the problem with the IPv6 address? Is the issue that the URL recorder does not support IPv6 addresses?
Hi Paul, We just open a socket and do not go out of our way to use V6 or find out if it's available on the system. After some research, I found that Vista installs IPV6 by default, it is active by default, and cannot be uninstalled (although it can be de-activated on a given network adapter manually, probably a bad thing to do). On Windows XP SP2, IPV6 is available and can be installed as an added protocol to each of the network connections. With IPV6 installed on XP, the same problem exists, except that commenting out the IPV6 localhost entry in the hosts file does not work, instead must modify the proxy setting on IE7 to use 127.0.0.1. Here is a link to some interesting JVM documentation regarding v6: http://java.sun.com/j2se/1.4.2/docs/guide/net/ipv6_guide/#ipv6-networking I agree with Tom Arman's notion that this problem shouldn't be there, that if both entries exist, the OS and/or IE should be trying both entries in the host table before giving up. So, I'm not sure if the problem is in IE or the protocol adapters. In any case, since V6 is active for Vista, it would not be surprising to find other Vista issues lurking in TPTP land.
(In reply to comment #5) Thanks Duwayne. This is more evidence that we need to complete a full test pass before we start 4.2.2 development to uncover anymore defects. I am assuming you were using TPTP 4.2.1.1 and Eclipse 3.2.1 for your testing?
(In reply to comment #6) When we are testing on Vista with TPTP 4.2.1.1, we should be using the lated 3.2 build (targeted as 3.2.2) which is the base for TPTP 4.2.2.
[Duwayne Morris] This should be fixed in 4.2.2. The fix has already been determined and can be implemented quickly (change to "127.0.0.1" versus "localhost" as the proxy string in the IE registry). A more sophisticated fix might be considered for 4.4.
Created attachment 56798 [details] Patch for HTTP recorder to fix localhost problem
Checked in the fix for this defect on Friday, Jan 12 after testing on Linux and Windows using all supported browsers, recording directly or through a proxy. Plan to file new defects to merge this change into other branches.
Please use this defect to check-in to 4.3.1 and 4.4 (HEAD).
Approval request: http://dev.eclipse.org/mhonarc/lists/tptp-pmc/msg02847.html
This has already been checked into tptp 4.4 and 4.3.1 as well as 4.2.2 under this defect number.
Reporter: Please verify and close in preparation for shutting down the TPTP 4.4 release. Thanks.
verified.
