Open imatasic opened 4 years ago
The "(null) - (null)"
is certainly a bug. I'll look into that. However, I'm not sure I understand your question below. What do you mean you can access both?
@allinurl in case i need access over both http and https, i have to run 2 instances of gwsocket. one with defined certificate and key, and one without.
Of course, they have to run on different ports, and I have to separately define them in apache site definitions with proxypass.
I have edited the original question to include the https proxypass definition
Please let me know if I can help you debug this in any way.
Ubuntu14.04 + Apache 2.4.7 + gwsocket 0.3 with SSL
I have found that if i serve both http and https traffic, and i have gwsocket service running like this:
/usr/local/bin/gwsocket_ssl --port=8080 --ssl-cert=/etc/apache2/ssl/apache_ss.crt --ssl-key=/etc/apache2/ssl/apache_ss.key --access-log=/tmp/gw_access.log
and access the site via http, this results in:
while accessing via https results in:
apache configs:
if i change proxypass directive in http site definition to watch port 8081, and run another instance of gwsocket like this, then i can access both: `/usr/local/bin/gwsocket_ssl --port=8081``
edit
/edit
Is this by design? is there a way to circumvent this, or should i be using two gwsocket services running on the same machine?