kdevan

Ok so it seems to me that `lib/util.js` sets the default configuration parameters. Then if the user provides some parameters of their own the connection object is created again in...

Lol well, I double checked and the value `0` is working. I must have tested this before that commit was made. You can ignore this. I'll leave it just in...

Maybe wouldn't hurt. But I can't think of any use cases off hand. I need to use ipv4 for development and ipv6 for stage/production and the `0` value does work...

This is great, I would not have thought to do it this way. I'm curious to learn more Golang as well as Caddy modules, so... perfect :) I'll give this...

I have tested this with something like the following and Caddy is booting up and running with no errors. ``` foo.bar.com:443 { bind tailscale/my-node tailscale_auth templates respond `Hello, {placeholder "http.auth.user.id"}}`...

I'm thinking about writing a transformer for Imaginary. I've looked at some of the other transformers to get a feel for it. I wonder if you have any advice for...

In my case a single server suits me well but I need to restart the server frequently due to scaling the server up when doing a bulk upsert and back...

@kishorenc Is there a reasonable solution for this that you can think of? I could try a PR, or could do a feature bounty for someone to try a solution...

For now I am excluding all query params using this option: ```js endpointOverrides: [ { pattern: /.*/, parameterFilter: (_name, parameter) => parameter.in !== 'query' } ] ```

Ran into the same issue with a single individual domain, not wildcard. The fix mentioned [here](https://github.com/libdns/route53/issues/235#issuecomment-2146454071) that ryantiger685 mentions worked for me. Looks like PRs in that repository need to...