On Fri, 14 Jan 2022 00:05:59 +0100
Jamo wrote:
> From: Javier Moragon
>
> I applied the last suggestion in this patch and I've finally realized
> how to use git send-email.
>
> I'm sorry for the unnecesary mails and I hope for next contributions
> I won't make the same mistakes, Thank you!
On Thu, 13 Jan 2022 23:14:54 +0100
Javier Moragon wrote:
> I'm sorry, it's my first time using a mailing list for publishing
> patches so I sent you the message directly instead of to grub-devel
> and my mail client wrapped the patch lines. I attached the patch
> Instead of pasting the diff, I
From: Javier Moragon
I applied the last suggestion in this patch and I've finally realized
how to use git send-email.
I'm sorry for the unnecesary mails and I hope for next contributions
I won't make the same mistakes, Thank you!
---
grub-core/net/http.c | 6 +++---
1 file changed, 3
I'm sorry, it's my first time using a mailing list for publishing
patches so I sent you the message directly instead of to grub-devel
and my mail client wrapped the patch lines. I attached the patch
Instead of pasting the diff, I hope this time the lines don't get
wrapped.
El jue, 13 ene 2022 a
On Wed, 12 Jan 2022 23:54:58 +0100
Javier Moragon wrote:
> According to https://www.ietf.org/rfc/rfc2616.txt 4.2, header names
> shall be case insensitive and we are now forced to read headers like
> `Content-Length` capitalized.
>
> The problem with that is when a HTTP server responds with a
>
According to https://www.ietf.org/rfc/rfc2616.txt 4.2, header names
shall be case insensitive and we are now forced to read headers like
`Content-Length` capitalized.
The problem with that is when a HTTP server responds with a
`content-length` header in lowercase GRUB gets stuck because HTTP
