James Hurst

Can you post the response headers you receive before trying to read the body? You can omit anything application specific / sensitive.

Three years later, I guess no one got around to this. If anyone wants to sponsor this I'd be up for it. Likewise, PRs welcome.

Can you post a minimal yet complete configuration to replicate the issue? Obviously if something this fundamental wasn't working we would know about it, so it's going to be a...

And you're getting `connection refused` only on the background worker connections, not the in-flight ones?

> Here's the config we use for proxying to Redis. This works, but of course is an extra step we'd love to avoid. Yeah, it really shouldn't be necessary. Are...

I'm closing this because I don't see that this could be a bug in `lua-resty-http`. I am certain that the method is being overridden elsewhere in the configuration, somehow. For...

This is never going to happen here. http2 doesn't really fit into lua-nginx-module cosockets very well, and that situation hasn't changed as far as I can tell. Square peg /...

The tests would seem to disagree with this: https://github.com/ledgetech/lua-resty-http/blob/master/t/18-parse_uri.t > in http.lua at line 260, the parse regex failed when the url like "xxx.yyy.com/config/list"; the fixed regex may like [[^(?:(http[s]?)://)?...]]...

> maybe [lua-resty-socks5](https://github.com/starius/lua-resty-socks5) should help. I haven't tested this, but yes I agree that would be the right approach.

It can be either. A badly formed request may return `nil, err` -- for example if the URI cannot be parsed correctly -- before attempting to make a connection. But...