`server-host=!6` also binds to ipv4

[steve-chavez]

Problem

We document that !6 should only bind to ipv6, however a request using ipv4 succeeds

$ PGRST_SERVER_HOST='!6' postgrest-with-postgresql-16 postgrest-run

$ curl localhost:3000/projects  --ipv4 -I
HTTP/1.1 200 OK

Notes

Using !4 works as expected:

PGRST_SERVER_HOST='!4' postgrest-with-postgresql-15 postgrest-run

$ curl localhost:3000/projects  --ipv6 -I
curl: (7) Failed to connect to localhost port 3000 after 0 ms: Connection refused

[wolfgangwalther]

Did you find out whether this and #3203 are actually bugs on our side or in the lib we are using?

[steve-chavez]

@wolfgangwalther Are you able to reproduce? Not sure if this could be OS-specific.

Did you find out whether this and #3203 are actually bugs on our side or in the lib we are using?

It must be the lib, we only do this:

postgrest/src/PostgREST/App.hs

Line 95 in 71887e4

& setHost (fromString $ toS configServerHost)

• https://hackage.haskell.org/package/warp-3.4.0/docs/Network-Wai-Handler-Warp.html#v:setHost
• https://hackage.haskell.org/package/warp-3.4.0/docs/Network-Wai-Handler-Warp.html#t:HostPreference

[wolfgangwalther]

Are you able to reproduce? Not sure if this could be OS-specific.

I did not try to. I was just wondering, because ...

It must be the lib, we only do this:

... that's what I remembered.

So if you can reproduce this with plain warp, then it would probably be better to raise this upstream.

[laurenceisla]

So if you can reproduce this with plain warp, then it would probably be better to raise this upstream.

I'm testing the library right now to confirm this. The "funny" thing is that * does not seem to accept ipv6 requests.

$ PGRST_SERVER_HOST='*' postgrest-with-postgresql-16 postgrest-run

$ curl localhost:3000/projects  --ipv6 -I
curl: (7) Failed to connect to localhost port 3000 after 0 ms: Couldn't connect to server

[steve-chavez]

@laurenceisla That looks the same as #3203

[laurenceisla]

@steve-chavez True, didn't check that.

[laurenceisla]

Made a gist with the tests I did:

https://gist.github.com/laurenceisla/61af763fb028437f24e5a869225eb1f8

The behavior is the same with Warp only.

[laurenceisla]

I submitted the issue upstream here: yesodweb/wai#976

[taimoorzaeem]

Fixed this in upstream fpco/streaming-commons#83 🚀. I will try do a new release of streaming-commons in some time.