Re: [users@httpd] httpd reverse proxy pass username per http_header

Hi, I just found http://serverfault.com/questions/207301/get-the-authenticated-user-under-apache which suggests: RewriteEngine On RewriteCond %{LA-U:REMOTE_USER} (.+) RewriteRule . - [E=RU:%1] RequestHeader set X-Remote-User "%{RU}e" env=RU And that exactly does the trick. KR

[users@httpd] Re: cross-compiled httpd 2.4.9: Segmentation fault. 0x403428ec in pthread_mutex_lock () from /lib/libc.so.0

I managed to solve this myself. It turns out that whenever you link a binary against libdb, you must also explicitly link it against libpthread, even though libdb is linked against libpthread itself. Otherwise - segfault. A target/uClibc/toolchain peculiarity? Very odd, but at least apache works no

[users@httpd] Proxy pass

Apache 2.4.10. This use to work: a request from https://share.domain.tld would find our Apache server. Apache would pass it to the tomcat app running on the same server port 8443. Since going to Apache 2.4.10, this no longer works. Here is the vhost: This rewrites https://share.anydomain.tld

Re: [users@httpd] Proxy pass

On Mon, Jan 19, 2015 at 2:33 PM, Chris Arnold wrote: > Is there something extra for this to work on Apache 2.4.10? Compared to what previous level? LogLevel rewrite:trace8 and the error log would be a big help. -- Eric Covener cove...@gmail.com

Re: [users@httpd] Not Listening on 443

On 01/16/2015 11:12 PM, Chris Arnold wrote: One of these defines isn't set. Where should it be set? The SSL VHost has VHost info... .. - Personally, I'd drop all of those IfDefine container

[users@httpd] RewriteMap values including query strings

I'm working on adding some 301 redirects for some sites we're migrating. I've been given a large list of 1:1 redirects. The majority of URLs include a query string. I've included the the full 1:1 URL mapping list in my redirect map text file. I'm finding issues when testing the URLs that contain

[users@httpd] Apache Not Starting

Apache 2.4.10. I am having 1 heck of a time getting 2.4.10 working. Now, apache is not starting: sudo systemctl start apache2.service Job for apache2.service failed. See "systemctl status apache2.service" and "journalctl -xn" for details. webtest:~ # systemctl status apache2.service -l apache2.