It's worth noting the client's connection will forever run through the proxy. This was ok for us because the connection was simply being sent to a pure kafka-ws gateway. On Aug 19, 2015 2:00 AM, "C Anthony Risinger" <[email protected]> wrote:
> You could try something like this: > > > http://uwsgi-docs.readthedocs.org/en/latest/Snippets.html#authenticated-websocket-proxy > > we ended up abandoning kafka for the kafka-shaped problem, but the > proxy-auth impl worked exactly like you want. The premise here is you use > rpcvar: to check "stuff" via the running app, then offload the connection > (or not) based on that response. > > -- > > C Anthony > > On Tue, Aug 18, 2015 at 7:54 PM, Andrew Stuart < > [email protected]> wrote: > >> Hello >> >> I have several application servers at the back end. >> >> I want all inbound requests to go through some authentication and >> authorization logic. >> >> I’m wondering is it possible to have a wsgi application that does the >> auth logic, and if the auth logic succeeds, then the request is proxied on >> to some other server (perhaps a remote server or perhaps a local wsgi >> application) for execution? >> >> thanks >> >> as >> >> _______________________________________________ >> uWSGI mailing list >> [email protected] >> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >> > > > > -- > > C Anthony >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
