Jdomain support sockets? about ngx_upstream_jdomain HOT 1 CLOSED

Hi @lancergon sorry for the late response. I am curious if you still have not figured it out. I wanted to ask if you had ever managed to have something working with this config but without jdomain entirely. I could be wrong but I spot some peculiarities with your config.

Firstly, you use server_name http://proxy; which has two problems. Firstly, you shouldn't include the protocol scheme in your server_name directive and secondly, I don't see you actually using a host header of proxy when you make your connection. So I don't believe that nginx will select this server block even if you connect to nginx on port 80.

The next thing I noticed has to do with your location blocks. It looks to me like the connection you're trying to establish maps to your second location block, but this location block is defined to have the prefix /api/notifications_alert while you're requesting /test_arch/api/notifications_alert. Forgive me if I'm missing some details here but it seems that location won't match.

What's more, even if your request was processed by that location block, I don't see how it would handle the request. I think you may have a typo in the configuration, as you define a variable $test_notifications_alert, but proxy_pass to a variable $test_arch_notifications_notifications_alert which is not defined anywhere else in the config you've included here.

I'm going to mark this issue closed since it's been open a long time without follow up (sorry again about that). Comment back if you have concerns or want it reopened.

from ngx_upstream_jdomain.