Running behind Apache

#1

Hello,

first websockets with Autobahn are really cool.

My Problem is that I have an Apache running on port 80 and I don’t know

how the Apache and Autobahn can work together, maybe mod_wsgi helps?

Is there some kind of recipe how to make Autobahn work with Apache?

Thanks,

Marco

0 Likes

#2

Hi Marco,

no, mod_wsgi won't cut it. You might try:

http://httpd.apache.org/docs/2.4/mod/mod_proxy_wstunnel.html
http://stackoverflow.com/questions/17649241/reverse-proxy-with-websocket-mod-proxy-wstunnel

I haven't tried, but from what they announce, that _should_ work.

Keep in mind that scaling to large numbers of connections (>1000) will likely be problematic/impossible due to the design of Apache.

Hope this helps. If you get it working, would be nice if you post your
experience here ..

/Tobias

···

Am 14.10.2013 11:30, schrieb Marco Schrank:

Hello,

first websockets with Autobahn are really cool.

My Problem is that I have an Apache running on port 80 and I don't know
how the Apache and Autobahn can work together, maybe mod_wsgi helps?

Is there some kind of recipe how to make Autobahn work with Apache?

Thanks,
Marco

--
You received this message because you are subscribed to the Google
Groups "Autobahn" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to autobahnws+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

0 Likes

#3

Hello Tobias,

thanks for your quick answer. I will try the links and

post my results within this thread.

Maybe I have a wrong perspective. Could you please tell

me what is the prefered way to deal with Autobahn from the server side?

Shoud it run standalone as a daemon?

Marco

0 Likes

#4

Hello Tobias,

thanks for your quick answer. I will try the links and
post my results within this thread.

Thanks!

Maybe I have a wrong perspective. Could you please tell
me what is the prefered way to deal with Autobahn from the server side?
Shoud it run standalone as a daemon?

For production use, either

1) run Autobahn standalone (it's quite capable .. we've tested up to 180k concurrently active WebSocket connections with Autobahn running on a 2-core VM with 4GB Ram - and you don't have a 2nd source of security issues)

2) run it behind a _capable_ and WS-aware Web server: nginx

3) run it behind a L4 loadbalancer/firewall: OpenBSD/relayd/pf

4) run it behind a WS-aware L7 loadbalancer/proxy: haproxy

In general, I'd go with 1) or 2) unless you have specific needs and
know what you are doing ..

Apache is getting ooold;)

/Tobias

···

Am 14.10.2013 16:33, schrieb Marco Schrank:

Marco

--
You received this message because you are subscribed to the Google
Groups "Autobahn" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to autobahnws+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

0 Likes

#5

Hello Tobias,

For production use, either

  1. run Autobahn standalone (it’s quite capable … we’ve tested up to
    180k concurrently active WebSocket connections with Autobahn running on
    a 2-core VM with 4GB Ram - and you don’t have a 2nd source of security
    issues)

I will try the first option. Seems to be more than capable of what I need.

In case that I figure out the Apache issue, I will post it here.

Thanks a lot for your help.

Marco

0 Likes