Hi, @corvid: while debugging the CSS loading patch, I noticed that sometimes dillo doesn't get the close after transfer event. This is needed to trigger the CSS parser with a full sheet. For instance, go to http://localhost:631/ (CUPS interface), and the progress bar will not get inactive after the page is got. Now, if you switch http.c to HTTP/1.0 queries, it will work as expected. Is there something missing, or a way to hook this? -- Cheers Jorge.-
Jorge wrote:
@corvid: while debugging the CSS loading patch, I noticed that sometimes dillo doesn't get the close after transfer event. This is needed to trigger the CSS parser with a full sheet.
For instance, go to http://localhost:631/ (CUPS interface), and the progress bar will not get inactive after the page is got. Now, if you switch http.c to HTTP/1.0 queries, it will work as expected.
Is there something missing, or a way to hook this?
Searching for "cups" and "Connection: close", I found http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504727 which says: | The client uses HTTP 1.1 and includes the |"Connection: close" header meaning that he wants that request to |be the last one. cups replies with a "Connection: keep-alive" |header and doesn't close its end of the connection, which is in |violation of the HTTP 1.1 RFC.
participants (2)
-
corvid＠lavabit.com -
jcid＠dillo.org