Matt Wilson schrieb: > On Sep 25, 3:17 pm, Christopher Arndt <[EMAIL PROTECTED]> wrote: > >> A client which does not supply the content-length for a POST request is >> not HTTP 1.0 compliant. From the RFC [1]: >> >> "A valid Content-Length is required on all HTTP/1.0 POST requests. An >> HTTP/1.0 server should respond with a 400 (bad request) message if it >> cannot determine the length of the request message's content." > > That's good to know. I'm working with a third-party vendor, and I > don't trust that they'll always include that information.
If they don't, immediatly botch the request. You *can't* possibly make sense out of it - based on what criteria would you consider the stream to be finished? If they chose to spoon-feed you one byte every fortnight, you wouldn't have a clue if it's fully transmitted or not. Diez --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
