Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[http] recognize status code 303 as valid #5

Closed
wants to merge 1 commit into from

Conversation

znull
Copy link

@znull znull commented Feb 25, 2012

According to RFC 2616 10.3.4, a 303 status is the proper http 1.1
behavior for what most http 1.0 clients did with code 302. Since ipxe's
http client advertises itself as http 1.1, it should recognize both.

Signed-off-by: Jason Lunz lunz@acm.org

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. Since ipxe's
http client advertises itself as http 1.1, it should recognize both.

Signed-off-by: Jason Lunz <lunz@acm.org>
@ipxe-devel
Copy link

On Saturday 25 Feb 2012 04:41:37 znull wrote:

According to RFC 2616 10.3.4, a 303 status is the proper http 1.1
behavior for what most http 1.0 clients did with code 302. Since ipxe's
http client advertises itself as http 1.1, it should recognize both.

Signed-off-by: Jason Lunz lunz@acm.org

Applied, thanks!

http://git.ipxe.org/ipxe.git/commitdiff/cb10137

Michael

@mcb30 mcb30 closed this Aug 14, 2012
cardoe added a commit to cardoe/ipxe that referenced this pull request Jan 26, 2017
The 'id' should always be the MAC address. We currently have no other
data for the name so make it the MAC address for now. ref ipxe#5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants