search

davidgfnet / wifi_display

E-ink wireless display
244 stars 36 forks source link

Fix for not having to chunk decode answer from server #7

Open X-Ryl669 opened 8 years ago

X-Ryl669 commented 8 years ago

By default, any HTTP/1.1 client must accept chunked encoded answer. For HTTP/1.0, it's not mandatory, and downgrading HTTP version to 1.0 is a lot less work than implementing chunked decoding on the ESP8266.

Also reduce UART speed used so it's possible to capture it via a serial terminal and UART adapter (115200 bauds is a standard rate for terminal, 460800 is not supported on mine). UART is not used anymore anyway for data transfer so it's a safe move.

davidgfnet commented 8 years ago

The server already takes care of not sending chunked responses. I agree that using HTTP1.0 works in any case but it seems a bit dodgy to me. Also unrelated change (baud rate change!)

X-Ryl669 commented 8 years ago

It does for Apache because it does not chunk if the content length is known beforehand (this is not the case with the other servers however).

Because the compression is not known beforehand, it's not very clean to set up a fixed content-length there. With the upcoming patches to remove the "fixed" content-length server side, this is required to avoid chunking.

Right, without the baud rate change, it can't debug the stuff, but I can split it in 2 PR.