I do not want to put anybody in trouble and I love node.js so far, but I do
not have the big deployment yet, so I am quirking through all possible
references for having the basics then (well, I have a CCNA...).
So I came along this:
> (i.e., if a Transfer-Encoding
header field is present). If a message is received with both a
> Transfer-Encoding header field and a Content-Length header field,
> the latter MUST be ignored.
>
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html (4.4)
This compared to:
> Sending a 'Content-length' header will disable the default chunked
> encoding.
>
http://nodejs.org/api/http.html#http_http_request_options_callback
So I do think of course node.js got here something right, that was wrong in
the dusty HTTP protocol... :D
Could one please elaborate on this?
Well, I saw @ry setting this manually or so in some video, but it was for
the PHP guys I guess (found it here: http://youtu.be/jo_B4LTHi3I?t=14m20s ,
watched it again, well. still same question :/ ).
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" 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/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
