rfc2616 - HTTP 1.1 TE header -


while reading rfc2616, came across te , transfer encoding headers chunked encoding. have following question on these:

  1. if http server rejects request because of presence of te header, rfc compliant?
  2. if http client sends request te header , list of t-codings , q values , once such q value 1, mandatory http server send response data encoding, eg: te: deflat;q=0.5 gzip;q=1 (does mandate server compress entity data in gzip , send or can server ignore , send data in normal way?).
  3. if http server not support reception of chunked data (i aware goes against rfc, intended), right error response code sent client client next time not send put request in chunked fashion.

thanks in advance valuable inputs , answers.

in rfc 7230 says,

the "te" header field in request indicates transfer codings,
besides chunked, client willing accept in response, and
whether or not client willing accept trailer fields in a
chunked transfer coding.

this infers te declaration client , can ignored next server. there should no reason http server reject request te header. if server not support chunked not support http 1.1 , therefore should interpret incoming request if 1.0 request , respond accordingly. see here.


Comments

Popular posts from this blog

database - VFP Grid + SQL server 2008 - grid not showing correctly -

jquery - Set jPicker field to empty value -

.htaccess - htaccess convert request to clean url and add slash at the end of the url -