Re: [users@httpd] slower https transfer speeds compared with rsync/smb/sftp

2018-01-11 Thread Adam Teale
256 464: MaxClients 256 466: SendBufferSize 1042560 2018-01-11 10:42 GMT-03:00 Adam Teale <a...@believe.tv>: > Hi Yann! Thanks for your help. > > The value for sendspace is "1042560" > ​What does that value mean? Is that how many bytes per packet​ can be sent >

Re: [users@httpd] slower https transfer speeds compared with rsync/smb/sftp

2018-01-11 Thread Adam Teale
03:00 Yann Ylavic <ylavic@gmail.com>: > On Thu, Jan 11, 2018 at 1:46 PM, Adam Teale <a...@believe.tv> wrote: > > Hey Eric thanks for letting me know about SendBufferSize, looking into it > > now. > > Any idea how to see what it currently defaults to via a command?

Re: [users@httpd] slower https transfer speeds compared with rsync/smb/sftp

2018-01-11 Thread Adam Teale
Hey Eric thanks for ​letting me know about SendBufferSize, looking into it now. Any idea how to see what it currently defaults to via a command? 2018-01-08 16:49 GMT-03:00 Eric Covener <cove...@gmail.com>: > On Mon, Jan 8, 2018 at 1:46 PM, Adam Teale <a...@believe.tv> wrote:

[users@httpd] slower https transfer speeds compared with rsync/smb/sftp

2018-01-08 Thread Adam Teale
Hi everyone, Firstly I hope this is an appropriate question for this list. I am looking into what could be causing decreased speeds when uploading/downloading files to our apache server via https. Can anyone suggest why upload/download transfers speeds in a web browser (Firefox, Chrome, Safari)

[users@httpd] Solved - WebSocket connections, reverse proxy, MacOS Server 5.2, django channels

2017-01-12 Thread Adam Teale
In case someone finds themselves in a similar situation here is how I got ​W eb ​S ocket connections working via Apache ​ in MacOS Server 5.2​ . And the solution ​i​ s simple. --- *The short version:​* ​I use MacOS Server 5.2 (ships with Apache 2.4.23) to

Re: [users@httpd] HTTP 401: Apache strips out response headers

2017-01-11 Thread Adam Teale
Marco I think I am experiencing this too. I am using apache to reverse proxy to our app that handles the web sockets / chat. As far as I can tell from mod_dumpio's logging apache returns the correct response headers to the client - particularly: [Wed Jan 11 09:31:43.807204 2017]

Re: [users@httpd] HTTP 401: Apache strips out response headers

2017-01-11 Thread Adam Teale
We are using apache​ 2.4.23 2017-01-11 9:33 GMT-03:00 Adam Teale <a...@believe.tv>: > Marco I think I am experiencing this too. > > I am using apache to reverse proxy to our app that handles the web sockets > / chat. > > As far as I can tell from mod_dumpio's logging ap

Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL

2017-01-05 Thread Adam Teale
Hi Yann thanks again for all your help. I am still trying to work out why the client isn't receiving the Upgrade header in the response. I see a proxy debug log: [Thu Jan 05 11:04:24.002173 2017] [proxy:debug] [pid 65956] proxy_util.c(3754): (54)Connection reset by peer: [client 127.0.0.1:51776]

Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL

2016-12-28 Thread Adam Teale
handle the request GET /chat/. Reason: Error reading from remote server 2016-12-28 11:57 GMT-03:00 Eric Covener <cove...@gmail.com>: > On Wed, Dec 28, 2016 at 9:53 AM, Eric Covener <cove...@gmail.com> wrote: > > On Tue, Dec 27, 2016 at 8:39 AM, Adam Teale <

Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL

2016-12-28 Thread Adam Teale
of mod_proxy, make sure the proxy submodules are include 2016-12-27 16:10 GMT-03:00 Adam Teale <a...@believe.tv>: > Perhaps something useful - I do see that the "serveradmin" command says > that it runs apache 2.2 even though "httpd -v" says 2.4.23?? > > httpd -v &

Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL

2016-12-27 Thread Adam Teale
Perhaps something useful - I do see that the "serveradmin" command says that it runs apache 2.2 even though "httpd -v" says 2.4.23?? httpd -v Server version: Apache/2.4.23 (Unix) Server built: Aug 8 2016 16:31:34 sudo serveradmin fullstatus web web:health = _empty_dictionary

Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL

2016-12-27 Thread Adam Teale
I have upgraded to MacOS 10.12 so now Apache 2.4.23 is the current version. Either way the patch that was suggested was supposed to have been included in 2.4.10. 2016-12-27 11:29 GMT-03:00 Adam Teale <a...@believe.tv>: > Otis do you know if it pretty straightforward to appl

Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL

2016-12-27 Thread Adam Teale
​Hi Daniel, Yes in the http_server_app.conf file it is activated: LoadModule ssl_module libexec/apache2/mod_ssl.so It is interesting though that when I run an "sudo apachectl -M" i can't see ssl_module in there. ​

[users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL

2016-12-27 Thread Adam Teale
Hi! I've been trying to setup a reverse proxy to a localhost websocket url. ProxyPass /chat/stream/ wss://localhost:8000/chat/stream/ ProxyPassReverse /chat/stream/ wss://localhost:8000/chat/stream/ I get an error in the apache error_log that reads: No protocol handler was valid for the URL