XMPP Service Operators - 2023-02-10

moparisthebest, with nginx, how do I redirect ALPN to Prosody while continuing to serve HTTP normally?

The example configuration on the wiki seems to assume that nginx will be used exclusively as a proxy, not that it will serve things on its own.

jonas’, snj’s stats page lists German and Portugese three times in the table at the bottom of the page, you might want to deduplicate languages there.

Link Mauve, tricky to do

de_DE vs. de_AT for instance, but in some cases, that is actually relevant

Is it de vs. de_DE vs. German?

German wouldn't parse and would be rejected

Ok.

Link Mauve, problem is I do the GROUP BY on the language tags inside the database, at that point I don't yet know whether the localized names will be equal

I could trim off the part behind the _, but I think that would be a highly contentious choice to do.

Link Mauve: I think the wiki example is correct, you can have as many streams and http servers hosted by the same nginx as you want, and it will forward traffic to itself

I'm still using sslh

moparisthebest, how do you do that, the stream to itself?

Link Mauve: like your https will be on a different IP or port, then that's your upstream in that stream config

Only the stream config can listen on your public 443

Oh, so I have to make all of my existing server sections to some other port, and then set that as an upstream?

And then it will open a socket to itself?

Yep

You can probably use Unix sockets for that now that I think about it

That sounds sub-optimal.

Should just be a free splice() call after the connect, I mean, what other way would be possible

It could handle the things internally, without yet another fd.

Nginx could for https things only I guess

But something is going to have to sit in front and multiplex to the others

Yeah, that’s exactly what I would want, nginx to handle HTTPS like it is currently doing, and proxy to Prosody for XMPPS stuff.

I guess you could ask