diff options
author | Jason Lunz | 2012-02-25 05:30:48 +0100 |
---|---|---|
committer | Michael Brown | 2012-03-01 17:16:53 +0100 |
commit | cb10137e1992ba8fcd035b228a6a58ba3b40c3a2 (patch) | |
tree | cafac0623dd81d0f5d4f2bcb829bf91b96f56e03 /src/net/tcp/httpcore.c | |
parent | [vmware] Fix length returned by guestrpc_command() (diff) | |
download | ipxe-cb10137e1992ba8fcd035b228a6a58ba3b40c3a2.tar.gz ipxe-cb10137e1992ba8fcd035b228a6a58ba3b40c3a2.tar.xz ipxe-cb10137e1992ba8fcd035b228a6a58ba3b40c3a2.zip |
[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>
Diffstat (limited to 'src/net/tcp/httpcore.c')
-rw-r--r-- | src/net/tcp/httpcore.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/src/net/tcp/httpcore.c b/src/net/tcp/httpcore.c index 3c36b8e0..69d27389 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; |