Test case showing persistent connection problem.

[jakecobb]

Test cases for tntim96/JSCover/#91

The single request tests will pass, but the consecutive request tests will fail.

[jakecobb]

In some sense the real problem here is that the Proxy-Connection: keep-alive header is getting passed through, causing the remote server to use a persistent connection. Updated the test to show header-based behavior and one that forces persistent connection attempts. Maybe we only want to fix the header-based tests as the other behavior would be a bug in the remote server (since HTTP/1.0 is non-persistent by default).

[tntim96]

Thanks for looking into this. Yes, after reviewing the code I came to the same conclusion. The server is ignoring the HTTP 1.0 protocol, but I've removed that proxy header anyway. You can download that build from here. Let me know if that works.

[jakecobb]

Thanks for the reply. The server is actually doing the right thing; HTTP/1.0 just defaults to non-persistent but the header overrides that. Proxy-Connection is non-standard but treated the same as Connection.

Your fix is incomplete because it only affects GET request with Javascript files, so it doesn't make any failing tests in this pull request pass (I only tested non-JS GET and POST). However, I rebased on top of your changes and was able to make the remaining fixes. Pull request #159 includes your most recent changes, these test cases, my fixes and some additional unit tests for the new code. It passes all tests and coverage checks for ant pre-commit.