From: Jason Lunz <lunz@acm.org>
Date: Sat, 25 Feb 2012 04:30:48 +0000 (-0800)
Subject: [http] Recognise status code 303 as valid
X-Git-Tag: v1.20.1~1991
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=cb10137e1992ba8fcd035b228a6a58ba3b40c3a2;p=thirdparty%2Fipxe.git

[http] Recognise status code 303 as valid

As RFC 2616 10.3.4 explains, a 303 status is the proper HTTP 1.1
behavior for what most HTTP 1.0 clients did with code 302.

Signed-off-by: Jason Lunz <lunz@acm.org>
Signed-off-by: Michael Brown <mcb30@ipxe.org>
---

diff --git a/src/net/tcp/httpcore.c b/src/net/tcp/httpcore.c
index 3c36b8e08..69d27389b 100644
--- a/src/net/tcp/httpcore.c
+++ b/src/net/tcp/httpcore.c
@@ -200,6 +200,7 @@ static int http_response_to_rc ( unsigned int response ) {
 	case 206:
 	case 301:
 	case 302:
+	case 303:
 		return 0;
 	case 404:
 		return -ENOENT;