lighty labs

2023-06-18

05:19 Lighttpd Support: RE: A 400 error introduced in v1.4.70 from Chrome(?)

according to the rfc this is apparently done for security reasons, aka to avoid compressing specific headers like :au... HenrikHolst

05:11 Lighttpd Support: RE: A 400 error introduced in v1.4.70 from Chrome(?)

but indexing the header is done by the sender if I read things correctly so looks like CEF (or perhaps CEF in some co... HenrikHolst

04:44 Lighttpd Support: RE: A 400 error introduced in v1.4.70 from Chrome(?)

Could be a bug in ls-hpack, looking at RFC 7541 both :authority and :path is labelled as static so AFAIK they should ... HenrikHolst

2023-06-16

17:10 Lighttpd Support: RE: A 400 error introduced in v1.4.70 from Chrome(?)

Since I now know exactly what causes the problem I will do a bit of deep dive into h2 next week and try to add loggin... HenrikHolst

14:04 Lighttpd Support: RE: A 400 error introduced in v1.4.70 from Chrome(?)

Unsure if it was the first request or if it was later in a reused connection. Regarding CEF it is my understanding th... HenrikHolst

13:40 Lighttpd Support: RE: A 400 error introduced in v1.4.70 from Chrome(?)

and since they claimed that it worked if they changed from using DNS name to ip I guess that it is :Authority: that i... HenrikHolst

13:39 Lighttpd Support: RE: A 400 error introduced in v1.4.70 from Chrome(?)

gstrauss wrote in message#11052:
> > Man thanks, reverted 4b9581ad and the problem disappeared so under some extreme... HenrikHolst

13:16 Lighttpd Support: RE: A 400 error introduced in v1.4.70 from Chrome(?)

gstrauss wrote in message#11050:
> FYI: commits related to h2 changes in lighttpd 1.4.70: commit:4b9581ad and commit... HenrikHolst

2023-06-15

22:18 Lighttpd Support: RE: A 400 error introduced in v1.4.70 from Chrome(?)

It was when I switched to 1.4.71 that we noticed the issue and it's a plain 400 so not a 403 and not a segfault. Anyw... HenrikHolst

2023-06-14

12:32 Lighttpd Support: RE: A 400 error introduced in v1.4.70 from Chrome(?)

And with unable to reproduce I mean that I have tested this in Chromium on Linux and Chrome and Edge in Windows 10 an... HenrikHolst