Re: [PATCH] web: http: Accept blank Content-Type headers.

Apologies for the previous email. I seriously botched some keystrokes. On Mon, Jul 27, 2015 at 5:05 PM, Mark H Weaver wrote: > David Thompson writes: > >> I encountered a bug in the HTTP header parsing bug when trying to >> download a file via Guix. The response had a Content-Type header, but

Re: [PATCH] web: http: Accept blank Content-Type headers.

On Mon, Jul 27, 2015 at 5:05 PM, Mark H Weaver wrote: > David Thompson writes: > >> I encountered a bug in the HTTP header parsing bug when trying to >> download a file via Guix. The response had a Content-Type header, but >> with no value, like so: >> >> Content-Type: >> >> From reading the

[PATCH] Add SRFI-25 implementation

Adds an implementation of SRFI 25 on top of Guile's native arrays. The implementation does not introduce a disjoint type; Guile arrays and SRFI-25 arrays can be used interchangably, though with different, partly conflicting APIs. * NEWS: Add preliminary, incomplete section on 2.0.12, noting the

Re: [PATCH] web: http: Accept blank Content-Type headers.

David Thompson writes: > I encountered a bug in the HTTP header parsing bug when trying to > download a file via Guix. The response had a Content-Type header, but > with no value, like so: > > Content-Type: > > From reading the W3C spec[0], an unknown Content-Type header can be > treated as