Comments on: HTTP Status: 100 Continue

By: Dan Kubb

Dan Kubb — Mon, 18 Aug 2008 07:42:03 +0000

For the specific example of uploading large files, what do you think about returning 413 (Request Entity Too Large)? It seems that this provides the user agent with more information than a 417 (Expectation Failed) status does, and is more specific in describing the problem.

By: Akki

Akki — Wed, 30 Apr 2008 14:02:02 +0000

Hi,

I was wondering if there was a response status to allow a large file to be “served” in parts and in just one response?

I need a way to do this and I’d be grateful if the pedant offers succor

thanks!

By: Ben Ramsey

Ben Ramsey — Mon, 28 Apr 2008 14:30:32 +0000

Ralf, I recommend you read the section in the PHP manual on the use of the header() function. In short, if you need to send the 100 Continue code, you may do so like this:

header(‘HTTP/1.1 100 Continue’);

If you are building a client application and need to check for the 100 Continue and other headers in a response received from the server, you can you curl, fsockopen, or something like Zend_Http.

Be aware that the Content-Length header cannot be trusted. The value it contains should only be considered for informational purposes and may not be the actual size of the uploaded file. However, with a request containing an Expect: 100-continue header, there won’t be a file uploaded, so you have only the Content-Length header to go by for determining whether or not to tell the client to continue sending the full request.

By: Ralf Jones

Ralf Jones — Mon, 28 Apr 2008 11:33:18 +0000

Can use 100 in PHP ?
As I know, PHP will save the file uploaded to /tmp first whatever u do
How to check “Content-Length” before the file saved?

By: Richard Harrison

Richard Harrison — Wed, 23 Apr 2008 23:59:10 +0000

Amazon’s S3 service uses this (if you want to play around with something in the wild).

By: julien-pauli

julien-pauli — Wed, 23 Apr 2008 10:01:13 +0000

Keep going Ben, HTTP is a wonderfull and powerfull protocol, show us what it can do in real world !
(Chris Shifflet’s HTTP developer’s Handbook is very nice)

By: Christian Flickinger

Christian Flickinger — Wed, 23 Apr 2008 02:06:19 +0000

Great post! You always enlighten me on things I take for granted… like http status codes!

They seem so hidden and untouchable, and you just want to use the standard 300/404/500…

The uses for some of them are very intriguing, and at least this one, 100, can significantly reduce overhead… instead of sending that 100mb file each time, then verifying details.. you can now verify before sending! GENIUS.