From: Birnbaum, D. J <dj...@pi...> - 2011-11-05 22:23:14
|
Dear Peter (cc eXist-open), Thank you for the quick response. At your suggestion, I added "RequestHeader unset Authorization" to the Location directive. If I understand correctly, the effect is supposed to be to prevent the credentials used to authenticate to apache from being passed along to eXist. This seems to have worked in that when I now start the Java administrative client I fill in my eXist administrative credentials and set the destination as xmldb:exist://exist.example.com/xmlrpc. When Apache challenges me, I fill in my Apache credentials (different userid and password than eXist) and it accepts them and lets me in to the eXist collections. That is, this fix resolves the problem where eXist was receiving and trying to process the Apache credentials from the Apache authentication in place of the eXist credentials that I had supplied in the client's original dialog. Alas, once I'm in I can't do anything. There are at least two problems: 1. The display is badly garbled, with a lot of missing letters in the text areas (e.g., the word "missing" might appear as "m s g") and widgets appearing in the wrong places, offset by a centimeter or two. When I can find something to click on, I can click on it, so I was able to try to upload a file into the database, but ... 2. When I try to upload a file into the database, I get the following error message: Impossible to store a resource C:\Users\djb\Desktop\interlinear.html: networking error Additionally, all of the various other problems reported in my original posting are still in effect. Thanks again! I hope the other pieces of the puzzle are can now be resolved ... Best, David dj...@gm... -----Original Message----- From: Peter Stadler [mailto:st...@we...] Sent: Saturday, November 05, 2011 5:42 PM To: Birnbaum, David J Cc: exi...@li... Subject: Re: [Exist-open] proxying exist behind apache We are proxying eXist behind apache as well and are restricting access to our development site on the apache's part. Since we are using ldap our virtualHost configuration differs a little bit from yours but I ran into a similar(?) problem where the remedy was to add "RequestHeader unset Authorization" to the Location directive (requires mod_headers). Maybe that helps? Alle the best Peter Am 05.11.2011 um 22:11 schrieb Birnbaum, David J: > 1. Add a virtual host in httpd.conf, as follows: > > <VirtualHost *:80> > ServerName exist.example.com > ProxyPass / http://localhost:8080/exist/ > ProxyPassReverse / http://localhost:8080/exist/ > <Location /> > AuthType Basic > AuthName "eXist" > AuthUserFile /opt/misc/.htpasswd > Require valid-user > </Location> > </VirtualHost> -- Peter Stadler Carl-Maria-von-Weber-Gesamtausgabe Arbeitsstelle Detmold Gartenstr. 20 D-32756 Detmold Tel. +49 5231 975-665 Fax: +49 5231 975-668 stadler at weber-gesamtausgabe.de www.weber-gesamtausgabe.de |