Comment # 12 on bug 1226217 from Dirk Stoecker

> Isn't this wrong as per http spec?

It's not wrong, only superfluous (both state the same value). It get's wrong
because apache now always enforces chunked encoding ignoring the input.

If it would strip the content-length in the transfer encoding coming from the
script case because of the information in the link you provided I can live with
this. I don't think that combination is used anywhere that we have a receiver
relying on the content length and using transfer encoding. Also doesn't make
much sense anyway: If I know the length of the transfer at the beginning
chunked transfer is wasted bandwidth.