Re: [users@httpd] Fw: unsubscribe

On Thu, Feb 8, 2018 at 9:18 PM, Richards, Toby wrote: > I sent my unsubscribe message over seven hours ago. Why am I still getting > messages? Wrong target. users-unsubscr...@httpd.apache.org -

[users@httpd] Fw: unsubscribe

?I sent my unsubscribe message over seven hours ago. Why am I still getting messages? Respectfully Submitted, R. Toby Richards Network Administrator Superior Court of California In and for the County of San Luis Obispo (805) 781-4150 From: Richards, Toby Sent:

Re: [users@httpd] Help with ProxyPass and ProxyPassReverse

Please ignore this post. I knew I was looking at it and not seeing it and the act of sending the help request made me look again. Fixed now. Sorry for the noise. John === On Thursday 08 February 2018 20:31:45 John Iliffe wrote: > I have a HTTP mail client

[users@httpd] Help with ProxyPass and ProxyPassReverse

I have a HTTP mail client running on port 7080 on the server that must be proxied through Apache. Using a workstation, I can enter: http://192.168.1.7:7080/mail.html and it brings up the mail client correctly. I tried to use ProxyPass/ProxyPassReverse to move the mail client to run on

Re: [users@httpd] websocket header not passing a long with ProxyPass and mod_headers

Am 08.02.2018 um 19:50 schrieb Mark Nenadov: according to the docs, you can actually specify the protocol: https://httpd.apache.org/docs/2.4/mod/mod_proxy_wstunnel.html : "In fact the module can be used to upgrade to other protocols, you can set the upgrade parameter in the ProxyPass

Re: [users@httpd] websocket header not passing a long with ProxyPass and mod_headers

> according to the docs, you can actually specify the protocol: > > https://httpd.apache.org/docs/2.4/mod/mod_proxy_wstunnel.html : > > "In fact the module can be used to upgrade to other protocols, you can set > the upgrade parameter in the ProxyPass directive to allow the module to > accept

Re: [users@httpd] websocket header not passing a long with ProxyPass and mod_headers

On Thu, Feb 8, 2018 at 1:33 PM, wrote: > You are probably proxying with mod_proxy_wstunnel. It seems to me that > "Upgrade: WebSocket" is hard-coded in that module. > > Regards, > > Rainer Hi Rainer, Thanks. Yes, I am using mod_proxy_wstunnel and it appears

Re: [users@httpd] proxy_fcgi - force flush to client

2018-02-02 12:20 GMT+01:00 Hajo Locke : > > > Am 02.02.2018 um 07:05 schrieb Luca Toscano: > > Hello Hajo, > > 2018-02-01 13:20 GMT+01:00 Hajo Locke : > >> Hello Luca, >> >> Am 01.02.2018 um 09:10 schrieb Hajo Locke: >> >> Hello Luca, >> >> Am 01.02.2018 um

RE: [users@httpd] SSL Certificate Validation

I didn’t think you could have two virtualhost entries with the same IP/port. I would probably do this within with a single VirtualHost, myself. Something like this combined with the RewriteRule: RewriteCond %{HTTP_HOST} !^THE.CORRECT.HOSTNAME$ Rick Houser Web Engineer From: Dr James A

Re: [users@httpd] SSL Certificate Validation

The easiest way to do this is to make sure you have the correct hostname in the virtual host - the one that matches your certificate and another virtual host which has no hostname in it to catch all the other requests.   return a forbidden response for all requests!   RewriteEngine On

RE: [users@httpd] SSL Certificate Validation

In addition to fixing your certificate, you may have a reason to make sure the host header they send is correct. If they are reaching you via an alternate hostname or something that’s getting them to the correct IP, but shouldn’t be supported for your service, stopping them from doing that

Re: [users@httpd] websocket header not passing a long with ProxyPass and mod_headers

Hi Rainer, hi Mark, Zitat von Rainer Jung : Hi Mark, Am 08.02.2018 um 16:49 schrieb Mark Nenadov: Hello, I have an operational setup where Apache httpd is proxying secure websockets traffic to an Apache Tomcat server. In other words, I'm using ProxyPass to pass

Re: [users@httpd] websocket header not passing a long with ProxyPass and mod_headers

Hi Mark, Am 08.02.2018 um 16:49 schrieb Mark Nenadov: Hello, I have an operational setup where Apache httpd is proxying secure websockets traffic to an Apache Tomcat server. In other words, I'm using ProxyPass to pass traffic along to a WSS url. I'm now having some issues trying to throw

Re: [users@httpd] SSL Certificate Validation

On Thu, Feb 8, 2018 at 7:36 AM, Belmona, Nizar wrote: > Thanks Rainer and Daniel. > > Sorry for the confusion and please let me clarify. > > > > We have a web server with Apache 2.2.22 with OpenSSL 0.9.8t, the Apache > service launches fine and the users/developers are

[users@httpd] websocket header not passing a long with ProxyPass and mod_headers

Hello, I have an operational setup where Apache httpd is proxying secure websockets traffic to an Apache Tomcat server. In other words, I'm using ProxyPass to pass traffic along to a WSS url. I'm now having some issues trying to throw mod_headers into the mix. I'm attempting to manipulate the

RE: [users@httpd] SSL Certificate Validation

Thanks Rainer and Daniel. Sorry for the confusion and please let me clarify. We have a web server with Apache 2.2.22 with OpenSSL 0.9.8t, the Apache service launches fine and the users/developers are able to connect however developers through their code bypass the Server SSL certificate

Re: [users@httpd] SSL Certificate Validation

Hello Nizar, You need to provide much more info on your current setup so we can provide any meaningful advice. Which SSL verification? What configuration? Regarding httpd what's needed in config, the basic thing to have "SSLVerifyClient require" and a list of accepted CA's but that could be

Re: [users@httpd] symbol SSLv2_client_method

Am 07.02.2018 um 11:03 schrieb Stefan Eissing: Your openssl is not the version that your apache was compiled against. If you updated it, you need to also re-compile any executables that link it. Note that running SSL without staying on current software versions is highly discouraged. For