HelloBug0
HelloBug0
Sorry, I am not quite clear [minutes and day] in limit-count plugin. Do you mean the time_window parameter in minutes or in day?
> > Sorry, I am not quite clear [minutes and day] in limit-count plugin. Do you mean the time_window parameter in minutes or in day? > > Yes ,I mean...
Is it a good idea if we organize some parameters of schema properties, like count, time_window, key, rejected_code, etd to a array? Than we cann deal with all these limiters...
> We should also deal with redis backend too? I think we could do that just as we do now.
DCID length is [8,20] bytes according to RFC9000 [at least 8 bytes](https://github.com/HelloBug0/hellobug0.github.io/blob/main/quic/png/DCID-8.png) [no more than 20 bytes](https://github.com/HelloBug0/hellobug0.github.io/blob/main/quic/png/DCID-20.png)
When we send a http request using `Range: bytes=724-817,888-927,859-931,449-,404-429,860-957,14-18,530-627`, the response status code is 206, and content type is `Content-Type: multipart/byteranges;`. Content length includes the length of boundary, Content-Range and...
When the HTTP request header contains `Range`, I think returning 206 is reasonable. @climagabriel