I am running httpd-2.4.6 on CentOS7. I have an https virtual host
configured to proxy requests to a specific location as wss
ProxyPass "wss://127.0.0.1:9000/"
ProxyPassReverse "wss://${server_name}/ws/"
However, attempts to connect occasionally fail, using curl to test:
curl -i -N -H "Co
Hello,
I'm trying to use an authz_dbd query to authorize based on the value
of a cookie (ie. if PHPSESSID cookie is set, a db query can test if it
should be authorized). It seems the only parameter AUTHzDBDQuery will
supply to the sql query is the username in place of %s; this could work
if I c
I have finally moved to Apache Httpd 2.4 from 2.2 and I am having issues
getting our basic authentication to our ldap for some very specific areas.
Below is what our 2.2 configuration used and worked just fine and the new 2.4
config that is not working. When I use the 2.4 it prompts for username
I'm starting to think you don't know what you need, and we don't understand
what you want. So, drop everything you (think you) know, and start over.
What are you trying to do? Not how you're trying to do it, or why, but
WHAT do you want to do? WHAT components are involved?
I'm thinking it's al
When you mention the DocumentRoot, do you mean just the setting for vhosts or
the document root for the reverse proxy? Are you telling me I don't need a
directive if I have a ProxyPass "/" "http://target/"; line?
And is it fine to have the ProxyPass defined like this:
ProxyPass "/"
"E:/progra
Testet again with clean Ubuntu 18.04.1 LTS and default Ubuntu repositorys
Apache 2.4.29-1ubuntu4.3
Openssl 1.1.0g-2ubuntu4.1
Same issue.
Von:"Frank Wuttig"
An: users@httpd.apache.org
Datum: 25.09.2018 08:25
Betreff:[users@httpd] tls_process_client_certificate:certificate
ver
