You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
<IfModule mod_ssl.c>
<VirtualHost _default_:443>
ServerName servername
ServerAlias servername
ServerAdmin webmaster@localhost
SSLProxyEngine on
ProxyPass"/wss""wss://127.0.0.1:8080/"ProxyPassReverse"/wss""wss://127.0.0.1:8080/"ProxyRequests Off
DocumentRoot /var/www/html
<Directory /var/www/html>
Options -Indexes +FollowSymLinks -SymLinksIfOwnerMatch +MultiViews
AllowOverride None
Require all granted
</Directory>
ErrorLog ${APACHE_LOG_DIR}/se_error.log
CustomLog ${APACHE_LOG_DIR}/se_access.log combined
SSLEngine on
SSLCertificateFile /etc/apache2/ssl/apache_ss.crt
SSLCertificateKeyFile /etc/apache2/ssl/apache_ss.key
<FilesMatch "\.(cgi|shtml|phtml|php)$">
SSLOptions +StdEnvVars
</FilesMatch>
<Directory /usr/lib/cgi-bin>
SSLOptions +StdEnvVars
</Directory>
BrowserMatch"MSIE [2-6]" \
nokeepalive ssl-unclean-shutdown \
downgrade-1.0 force-response-1.0
# MSIE 7 and newer should be able to use keepaliveBrowserMatch"MSIE [17-9]" ssl-unclean-shutdown
</VirtualHost>
</IfModule>
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``
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?
The text was updated successfully, but these errors were encountered: