Hi Luca, could you explain what 404 and 406 error codes means? ... are this errors related to each others or they indicate that there are two different problems?
On Fri, 4 Mar 2016 at 15:22 Luca Verardi <[email protected]> wrote: > Hello everybody, I'm having problems using tgext.socketio's available > websockets, frequently running into HTTP 404 or 406 errors. > Web requests are served by Apache 2.2, and I can't update it due to > workspace constraints. > Even compiling wstunnel for Apache didn't solve the problem. > This is the current configuration for VirtualHost: > > ProxyPass /socketio ws://localhost:8081 > ProxyPassReverse /socketio ws://localhost:8081 > > My app's software stack contains: > > TurboGears2 2.3.7 > tgext.socketio 0.0.1 > > and my [server:main] is: > > use = egg:tgext.socketio#socketio > socketio_resource = socketio > host = 0.0.0.0 > port = 8081 > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/turbogears. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/turbogears. For more options, visit https://groups.google.com/d/optout.
