Vladislav

Hi! I'm running ```bash wget "https://github.com/CrowCpp/Crow/releases/download/v1.0%2B4/crow_all.h" g++ test.cpp # gcc 11.2 or clang 13.0 ./a.out & sleep 1 && curl "http://0.0.0.0:18080/license?serial=10932847102398&period=984&licensee=EMoi" && fg ``` And its printing (as expected). ```...

This is definitely an interesting feature. > Justifications exist, but weak. Contrary to iterators from channels, this one would have no overhead and should be preferred if you don't work...

I'm afraid the won't be any more ideas 😢 The first option is not that bad actually, except for the `Close`. Having to close the iterator is ~~inconvenient~~ almost impossible,...

> the question is whether https://github.com/Suor/django-cacheops tests pass - #184 They don't, because the comparison in the snippet fails. It expects a number on the left

`conj_key` is not passed anywhere - its generated in `conj_cache_key` ```lua -- the keys that are passed to EVAL local prefix = KEYS[1] local key = KEYS[2] local precall_key =...

@kang-sw @MichaelSB Sorry for the wait. The updates somehow got lost in my inbox 😰 There are indeed numerous bugs in the websocket code. First of all, as you pointed...

Hi! Indeed, Crow currently doesn't run middleware for OPTIONS/HEAD requests. Briefly, middleware runs for handlers. If there is no handler, then no middleware is run

@The-EDev: What do you think? What would be the best way of handling OPTIONS without breaking backwards compatibility. Maybe we can run local & global middleware if it has some...

Hi! Thanks for the fix! Sorry for the long wait 😓 Lets ask someone who might have windows on hand @The-EDev if he can reproduce the original bug. Else I'll...

You're right, it's not documented so far. Websockets are increasingly popular in crow, but unfortunately pretty rough so far. I wouldn't say its related to the async handlers issue because...