You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In connection_base.ipp file I see that you are only reading the response if the "Transfer-Encoding: chunked" is present when using Boost Connect as an HTTP client but there is no support for writing a chunked response when using BoostConnect as an HTTP server. I am correct?
The text was updated successfully, but these errors were encountered:
Maybe, your ideas are right. When using BoostConnect as an HTTP server, "class server" and "class http_session" is not support for writing a chunked response.
I could not conceive a good spec idea . So, support for writing a chunked response is not implemented. I can implement a little idea now. I should implement this idea?
Does the server part of BoostConnect have the possibility to send HTTP responses with "Transfer-Encoding: chunked" header?
http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.6.1
https://en.wikipedia.org/wiki/Chunked_transfer_encoding
In connection_base.ipp file I see that you are only reading the response if the "Transfer-Encoding: chunked" is present when using Boost Connect as an HTTP client but there is no support for writing a chunked response when using BoostConnect as an HTTP server. I am correct?
The text was updated successfully, but these errors were encountered: