* on the Wed, Mar 07, 2007 at 10:28:22AM +0000, Mike Cardwell wrote: > Using the standard Redhat Enterprise 4, Apache 2.0.52 RPMs here. I have > a CommunigatePro server. It runs it's own http daemon for the > administration interface, and webmail. We needed to extend it in several > ways, so I stuck an Apache mod_proxy in front of it. Here's the config I > used which works fine: > > ProxyPass / https://127.0.0.1:9100/ > ProxyPassReverse / https://127.0.0.1:9100/ > > However. When using webmail, if you go to view an attachment like for > example "filename.txt" from message "message_id" in folder "INBOX" the > url would look like: > > https://the.domain/session/session_id/MessagePart/INBOX/message_id/filename.txt > > That works absolutely fine. The problem is when the file is in a > subfolder, eg "INBOX/Archive". Then the url becomes: > > https://the.domain/session/session_id/MessagePart/INBOX%2FArchive/message_id/filename.txt > > With the url above, mod_proxy simply does *nothing*, I get an Apache 404 > error message because the path doesn't exist locally because mod_proxy > hasn't attempted to do the proxying. I've used tcpdump to verify that > there is no connection to port 9100 when I make the request. > > Is this a bug, or am I doing something dumb?
I found a solution to this problem. It's not a bug, just unexpected default behaviour I guess. I solved it over on the users list anyway. Sorry for wasting your time. Mike
