Kristaps Dz
Kristaps Dz
Running **-h** will get the usage message, so there's no need to implement it. Do you have a use case for needing the version of `lowdown`?
No: CSRF protection is orthogonal to kcgi, as you'd need some manner of persistent storage. If you're not scaling across machines, it's pretty easy and performant to just have an...
Excellent point. This has also revealed a bad encoding when encountering spaces in URLs in `-tman` and `-tms`. Thank you! I'll have this fixed in the next release.
`parse_ext_attrs` is the place one would look at to add this. If you'd like to take a stab at this, I'd refactor any `key=value` pair as being added to a...
Hi, I'm happy to help! Please contact me from the email address on my linked website and we can take about supporting this. Please keep in mind that I have...
What do other tools use?
Thank you for this! I've merged a form of the second one ("basic hit support"). I'm curious why you ended up adding the interval support instead of using the callbacks...
Excellent point. I'll start adding that in! It might look a little different in terms of API, but not much.
I see your point, but it's unlikely I'll do this myself. I'm happy to review and merge patches for this, however.
Good point with misusing the term "default" on my part. When `lowdown` is used without **--template**, it produces meaningful defaults, but it doesn't actually use the templates in `share`. I...