From ec0d1f9199433e1821ed56af549a9f567e432bf2 Mon Sep 17 00:00:00 2001 From: Graham Leggett Date: Fri, 27 Dec 2019 22:43:12 +0000 Subject: Remove section on RFC compliance. All listed PRs are resolved, thanks to the donation of access to the Co-Advisor test suite. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1872038 13f79535-47bb-0310-9956-ffa450edef68 --- STATUS | 12 ------------ 1 file changed, 12 deletions(-) (limited to 'STATUS') diff --git a/STATUS b/STATUS index 26adfcc0e2..354cfebc6b 100644 --- a/STATUS +++ b/STATUS @@ -201,18 +201,6 @@ RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP: Once we have a clean solution, we can try to optimize it, so that the server won't be slow down too much. - * RFC 2616 violations. - Closed PRs: 15852, 15857, 15859, 15861, 15864, 15869, 15870, 16120, - 16125, 16135, 16136, 16137, 16138, 16139, 16140, 16518, - 16520, 49825 - Open PRs: 15865, 15866, 15868, 16126, 16133, 16142, 16521, 42978 - jerenkrantz says: need to decide how many we need to backport and/or - if these rise to showstopper status. - wrowe suggests: it would be nice to see "MUST" v.s. "SHOULD" v.s. "MAY" - out of this list, without reviewing them individually. - wrowe asks: what is lingering after 2.4.25 release? Offhand, only - URI conformance - * pipes deadlock on all platforms with limited pipe buffers (e.g. both Linux and Win32, as opposed to only Win32 on 1.3). The right solution is either GStein's proposal for a "CGI Brigade", or OtherBill's proposal -- cgit v1.2.3