Ability to disable 'Transfer-Encoding: chunked'

[iSerganov]

Background

There are numerous legacy client devices for audio playback that doesn't support chunked Transfer Encoding.
At the same time they use HTTP/1.1 clients to request audio streams. Not supporting chunked Transfer-Encoding by HTTP/1.1 clients is a spec violation as RFC-7230 clearly says that HTTP/1.1 clients must do that. My guess is that the reason for such spec neglect is that not so long ago all Icecast/SHOUTcast streaming servers returned only HTTP/1.0 responses and never supported chunking.

Though all modern devices support chunking, this still appears to be quite a common case in streaming universe as thousands of legacy clients are still eager to access audio streams all over the world.

Fix

Actual fix to this issue is very simple: you detect a request from legacy device analyzing User-Agent HTTP header and add the following line to your code (Golang):

w.Header().Set("Transfer-Encoding", "identity")

But...

... this doesn't work if a streaming server is behind Nginx ingress controller which always returns
[http @ 0x600003d901e0] header='Transfer-Encoding: chunked' to all HTTP client requests until Content-Length header is specified. This behavior is 100% correct and spec compliant however breaks the fix from the previous paragraph.

Request

Is it possible to add control over Transfer-Encoding response header through e.g. new annotation:
nginx.ingress.kubernetes.io/disable-chunked-transfer-encoding: true?

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[longwuyuan]

Do you want to submit a PR ?

[iSerganov]

I think I can try!

[github-actions]

This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach #ingress-nginx-dev on Kubernetes Slack.

[longwuyuan]

@iSerganov we now have Nginx v1.25 which has chunking on by default.
Someone else enabling chunking in their application code and the ingress-controller logged duplicate chunking config messages #11162

I am not sure if you are still interested in this but its been open without activity for a long time. So I will close this for now and you can reopen it if you are going to work on a PR as per notes in this issue history. thanks you

/close

[k8s-ci-robot]

@longwuyuan: Closing this issue.

In response to this:

@iSerganov we now have Nginx v1.25 which has chunking on by default.
Someone else enabling chunking in their application code and the ingress-controller logged duplicate chunking config messages #11162

I am not sure if you are still interested in this but its been open without activity for a long time. So I will close this for now and you can reopen it if you are going to work on a PR as per notes in this issue history. thanks you

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.