Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
Hi, Gregory Boyce <gboyce-qL0WqcyiFk9Wk0Htik3J/w at public.gmane.org> writes: > Two things I noticed: > > 1) NTLM auth may not work properly via proxy. > > http://www.gossamer-threads.com/lists/apache/dev/312633 Interesting... And unfortunate. It does seem to be working in my tests, however I'm only testing with a single client at the moment so there would only be one necessary backend connection. Thank you for the link. > 2) disablereuse=on and keepalive=on are contractory. Both are > referring to the persistence of the backend connection rather than the > frontend. keepalive=on turns it on while disablereuse turns it off. The docs were very unclear on this.. I thought that disablereuse would prevent reuse of a backend connection from different frontend connections. But apparently it completely prevents backend connection reuse, even with multiple requests from the same frontend connection. Although this does somewhat explain why NTLM fails ;) >> ProxyRequests off >> ProxyPass / http://172.16.64.10/ timeout=300 disablereuse=on nocanon keepalive=on >> ProxyPassReverse http://172.16.64.10/ / >> ProxyPassReverseCookieDomain 172.16.64.10 127.0.0.1 >> ProxyVia off > > Is frontend persistence enabled somewhere else in the configuration? No, it wasn't. I found that configuration in httpd.conf and fixed that -- that was one of my problems. Thanks, -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH warlord-DPNOqEs/LNQ at public.gmane.org PGP key available
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |