summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2004-04-16 07:33:53 +0000
committerDaniel Stenberg <daniel@haxx.se>2004-04-16 07:33:53 +0000
commitf97d194934ed51a1be518c8e101baf235bbb1043 (patch)
treec4551166a248327226f1a5fb6c5d8e3b82fdd16e
parent4661cc7403ef0793cef29a1762fca19f114f0744 (diff)
downloadgnurl-f97d194934ed51a1be518c8e101baf235bbb1043.tar.gz
gnurl-f97d194934ed51a1be518c8e101baf235bbb1043.tar.bz2
gnurl-f97d194934ed51a1be518c8e101baf235bbb1043.zip
adding issue 36 to be fixed before release
-rw-r--r--TODO-RELEASE14
1 files changed, 14 insertions, 0 deletions
diff --git a/TODO-RELEASE b/TODO-RELEASE
index c0aa425ad..3f88bbcb1 100644
--- a/TODO-RELEASE
+++ b/TODO-RELEASE
@@ -6,6 +6,20 @@ Issues not sorted in any particular order.
To get fixed in 7.11.2 (planned release late April/early May 2004)
======================
+36. autobuild test failures on Tru64/IRIX (test case 88 for example)
+
+ The problem is once again (this is the same scenario we had before in the
+ notorious test case 91 failure bug hunt) that when doing a second request,
+ the client hasn't yet found out that the previous connection is on its way
+ to get closed. It then re-uses the connection only to find it closed right
+ away.
+
+ We have code starting at lib/transfer.c:1949 that is supposed to detect
+ this situation and enforce a retry. This retry never happens on these
+ failures, indicating that the check is bad or that some code has ruined the
+ values used in the check.
+
+
To get fixed in 7.12.0 (no date)
======================