hi Mark!
Yes you're right, the status code should be encoded in close-frame, not
HTTP response.
Sorry for the wrong patch. ;-)
Best regards.
On Wed, Aug 7, 2019 at 2:52 PM Mark H Weaver wrote:
> Hi,
>
> Nala Ginrut writes:
>
> > Hi folks!
> > The current response builder will reject status co
Hi,
Nala Ginrut writes:
> Hi folks!
> The current response builder will reject status code less than 600:
> ---code-
> ((not (and (non-negative-integer? code) (< code 600)))
> (bad-response "Bad code: ~a" code))
> ---
Here is a patch to add necessary status code, and avoid checking failure
when building response.
Based on branch stable-2.2
Thanks!
On Fri, Jul 26, 2019 at 2:06 PM Nala Ginrut wrote:
> Hi folks!
> The current response builder will reject status code less than 600:
> ---
Hi folks!
The current response builder will reject status code less than 600:
---code-
((not (and (non-negative-integer? code) (< code 600)))
(bad-response "Bad code: ~a" code))
---
H
