https://bz.apache.org/bugzilla/show_bug.cgi?id=60850
--- Comment #3 from Eric Covener <[email protected]> --- (In reply to nbmlaw from comment #2) > i have tried it with a blank CentOS installation on VirtualBox. just by > adding the file /etc/httpd/conf.d/vhosts.conf with > <VirtualHost *:80> > ServerName www.example.com > ServerAlias example.com > DocumentRoot /var/www/html/example.com/public_html > # ErrorLog /var/www/example.com/error_log > ProxyPass /.well-known ! > ProxyPass / http://example2.com/ > </VirtualHost> > <VirtualHost *:80> > ServerName www.example2.com > ServerAlias example2.com > DocumentRoot /var/www/html/example2.com/public_html > </VirtualHost> > (and adding example.com and example2.com to /etc/hosts) > i can see that it works fine. example.com passes to example2.com and i can > see a test file in .well-known. > > there must be a problem on my production server somehwere. the versions of > centos-release and httpd are identical > > do you know of any particular configuration that would specifically disable > the ! directive? Thanks for verifying. IMO Nothing like that is really plausible, the most plausible is that there are other proxying rules hidden somewhere (including e.g. RewriteRule ... ... [P]) if it hadn't persisted so long, I'd say another candidate is browser caching. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
