Closed anze555 closed 5 years ago
It was something obvious: if client doesn't supply username / password, authentication plugin is not called at all, and request is discarded silently. A log message would have saved me quite a few hours.
As far as I'm concerned, this issue is solved, closing.
Hi,
I am having trouble using HTTP backend - despite all my configuration efforts it doesn't issue a request to backend HTTP API, and instead rejects each subscribe request. I feel I must be missing something obvious, but I can't figure it out...
I have two docker containers, started with docker-compose:
mosquitto
andmyapp
.The myapp backend API is accessible from
mosquitto
container. If I start a terminal in themosquitto
container and do a curl request, I get the result:The
mosquitto.conf
is:Container logs reveal nothing unusual: (to me)
Listening with tcpdump in mosquitto container shows nothing is sent to destination port 80 anywhere:
I have tried:
1bc268535d526bfabea8dafb3a43d51bc5655b22
)be_jwt.c
, line 205 - trying to free a static array; but I don't need JWT anyway because it turns out one can't set headers with WebSockets)I am not 100% sure on how to use
auth_opt_http_ip
andauth_opt_http_hostname
, so I have tried multiple variations, but nothing worked.Am I missing something obvious, or does HTTP backend simply not work? I would appreciate some help...