CL_HTTP_CLIENT, Content-Length in multipart segment are not part of RFC 186

Question

Hi, we are generating http multipart request using class CL_HTTP_CLIENT, and multipart segments header are filled with Content-Type and Content-Length, by default. Both elements are not part od RFC 1867, and request is not working.
We find a way to avoid Content-Type in note 582889 "delete Content-Type of HTTP request header", but we can find anything to avoid content-length.
POST /TransporteBienes/SeguridadCliente/presentarRemitos.do HTTP/1.1
Content-Type: multipart/form-data; boundary=ejjeeffe0
Content-Length:       759
accept-encoding:
--ejjeeffe0
Content-Length:        11
content-disposition: form-data; name="user"
30663288497
--ejjeeffe0
Content-Length:         6
content-disposition: form-data; name="password"
We need to avoid content-length:
POST /TransporteBienes/SeguridadCliente/presentarRemitos.do HTTP/1.1
Content-Type: multipart/form-data; boundary=ejjeeffe0
Content-Length:       759
accept-encoding:
--ejjeeffe0
content-disposition: form-data; name="user"
30663288497
--ejjeeffe0
content-disposition: form-data; name="password"
Is there any way to do that?
Regards.

Answer 1

Anybody?